Skip to content
TYPO3API Hub

TYPO3, open to every application

Connect TYPO3 to your other systems through one secure REST API, not through a separate interface for each integration.

  • Ready to use: records and files through one API
  • One overview: all connected applications in one module
  • Full control: stop each application at any time
  • Your permissions: TYPO3 permissions apply to each request
Illustration of a server, a browser window, documents, a chart and a speech bubble, each connected through a gate to one central hub.

How API Hub connects your systems

All applications use one controlled API. Your content stays in your TYPO3 installation, and your permissions apply.

One API instead of many interfaces

Usually, each integration has its own interface, keys and documentation. You must maintain all of them. API Hub gives all your applications one API.

  • Faster integrations: The API gives access to records and files.
  • Limited access: Each application gets only the selected access.
  • One overview: One module shows all applications with access.
  • Correct documentation: TYPO3 generates it from the code.
  • Known standards: The API uses OAuth 2.0, OpenAPI and JSON Schema
Read the business case
Example of four apps. The administrator selects the access for each app, independent of its app type.

You control the access

The access of an application is never more than the access of its backend user. It is also never more than an administrator selected. Page, table, field and file permissions and workspaces apply as in the backend.

Each request must pass all checks. The first failed check stops the request. API responses never contain passwords.
Access stops immediately

Disable an app. Its next request fails.

Passwords stay hidden

The API does not return passwords or password hashes.

Your data stays in your installation

API Hub operates in your installation and needs no additional service.

Read about security

REST API · OAuth 2.0 · Extensible

The REST API gives access to records and files. Applications authenticate with OAuth 2.0 or a static token, and scopes limit each application. Extensions add their own actions to the API. Other interfaces, for example for AI agents, can use the same apps, tokens and scopes. Each interface then has the same access control, and you manage all applications in one module.

Use cases

Monitoring

Connect workflow and monitoring tools. Each token gives access only to the necessary actions.

Imports and migrations

Move content into TYPO3 with the same validation as in the backend. Use a workspace to review the content.

Part of the TYPO3 Suite

The release of API Hub for TYPO3 14.3 is on 9 November 2026, as part of the TYPO3 Suite. The TYPO3 Company submitted this feature for integration in TYPO3 v15, and it will likely be part of it. You can use API Hub before the next major version.

Manufacturer responsibility

For Suite components, the TYPO3 Company is the manufacturer under the EU Cyber Resilience Act.

Long-term support

Each Suite version gets updates and up to 7 years of support. Supported versions get ELTS access.

Access through partners

Your TYPO3 partner sets up the access and helps you. See the offer of the TYPO3 Suite.

Status and adoption

Select your role

Illustration of steps leading up to a central hub.

Decision makers

Read about the changes, the necessary work and the fit for your project.

Business case, security and status
Illustration of blocks passing through a gate with switches.

Administrators

Connect applications, select scopes and remove access in the backend.

Manage apps and access
Illustration of a hub with a ring. A segment moves into the ring.

Developers

Install the extension, call the API and provide your own actions.

Quick start, cookbook and API