Use cases
These examples show how organizations can use API Hub, and the access for each case. All cases use the same API and the same access control.
A monitoring or workflow tool checks pages or finds changes in content. Its token can only read. An error in the tool cannot change content.
Move product data, press releases or an old website into TYPO3. The validation is the same as in the backend. Editors can review the result in a workspace before the publication.
A service gets content, returns the result and uses images and documents. Each supplier uses the same interface.
Editors connect an external tool and approve the access. The tool uses their permissions. Each editor sees only the permitted content.
Your developers add a function to an extension one time. The API and the backend can then use it, with validation, documentation and access control.
An agent uses the REST API with a token, as all other apps do. The same limits apply.
A monitoring or workflow tool checks pages or finds changes in content. Its token can only read. An error in the tool cannot change content.
Automation and monitoring
A monitoring or workflow tool checks pages or finds changes in content. Its token can only read. An error in the tool cannot change content.
Move product data, press releases or an old website into TYPO3. The validation is the same as in the backend. Editors can review the result in a workspace before the publication.
Imports and migrations
Move product data, press releases or an old website into TYPO3. The validation is the same as in the backend. Editors can review the result in a workspace before the publication.
A service gets content, returns the result and uses images and documents. Each supplier uses the same interface.
Translation and content services
A service gets content, returns the result and uses images and documents. Each supplier uses the same interface.
Editors connect an external tool and approve the access. The tool uses their permissions. Each editor sees only the permitted content.
Applications for editors
Editors connect an external tool and approve the access. The tool uses their permissions. Each editor sees only the permitted content.
Your developers add a function to an extension one time. The API and the backend can then use it, with validation, documentation and access control.
Custom business logic
Your developers add a function to an extension one time. The API and the backend can then use it, with validation, documentation and access control.
An agent uses the REST API with a token, as all other apps do. The same limits apply.
AI assistants and agents
An agent uses the REST API with a token, as all other apps do. The same limits apply.
Select the access#
content:readcontent:read and content:writeadmin in addition| The application… | Connect it with | Uses |
|---|---|---|
| operates on a server without a user | Static token | One dedicated backend user |
| has many users with different permissions | OAuth 2.0 | The person who approved it |
| must only read | The scope content:read | The user of the token |
| must change content | The scopes content:read and content:write | The user of the token |
| must manage backend users or other data for administrators | The scope admin in addition | An administrator only |