---
title: "Status and adoption"
description: "The available functions of API Hub, the integration into TYPO3 Core, the requirements and the steps of an adoption."
canonical: status.html
navigation-title: "Status"
---
# Status and adoption
- [Available functions](#available-functions)
- [What the TYPO3 Suite adds](#what-the-typo3-suite-adds)
- [TYPO3 Core](#typo3-core)
- [Requirements](#requirements)
- [Steps of an adoption](#steps-of-an-adoption)
- [Frequently asked questions](#frequently-asked-questions)
The release of API Hub for TYPO3 14.3 is on 9 November 2026, as part of the
[TYPO3 Suite](https://suite.typo3.com/). The TYPO3 Company submitted this
feature for integration in TYPO3 v15, and it will likely be part of it.
## Available functions
| Function | State | Notes |
| --- | --- | --- |
| Read and change records of all tables | [Available] | With FlexForms, workspaces and permissions |
| Manage files and folders | [Available] | The system log shows changes |
| Static tokens and OAuth 2.0 | [Available] | With consent screen and refresh tokens |
| Generated API documentation | [Available] | OpenAPI 3.1, available in the backend |
| Own actions and scopes in extensions | [Available] | See [Extending the API](../developer/index.md#developer) |
| Use by AI agents over HTTP | [Available] | With a token, as all other apps do |
| Part of TYPO3 Core | [Submitted] | Submitted for integration in TYPO3 v15, likely part of it |
## What the TYPO3 Suite adds
The [TYPO3 Suite](https://suite.typo3.com/) is a commercial delivery
channel for TYPO3 features. It is not a fork or a separate version of TYPO3
CMS. TYPO3 CMS stays free and open source.
For Suite components, the TYPO3 Company is the manufacturer under the
EU Cyber Resilience Act. You or your agency are responsible for your
code, your extensions and the integration in the project.
Each Suite version gets updates and up to 7 years of support. Supported
versions get ELTS access.
Only official TYPO3 Solution and Technology Partners can supply the
Suite. Your partner sets up the access and helps you in the project.
The [page of the TYPO3 Suite](https://suite.typo3.com/) describes
the current offer and the prices.
## TYPO3 Core
TYPO3 14.3 gets API Hub through the Suite, before the regular release cycle.
The TYPO3 Company submitted this feature for integration in TYPO3 v15 as
[patches for review](https://review.typo3.org/q/hashtag:actions), and it
will likely be part of it. The epic
[#111053](https://forge.typo3.org/issues/111053) tracks the work on the
Core.
The API uses OAuth 2.0, OpenAPI 3.1, JSON Schema and problem details.
This does not change with the delivery channel.
Each action has its own version. An incompatible change gets a new
version. The old version stays available until the next major version
of TYPO3. See [Versions and deprecation](../usage/endpoints.md#usage-versions).
## Requirements
- **TYPO3:** 14.3.10 or later
- **Delivery:** TYPO3 Suite, through a TYPO3 partner
- **PHP:** 8.2 or later
- **Installation:** Composer-based
- **Database:** Three additional tables, from the extension setup
- **Additional services:** None
- **License:** GPL-2.0-or-later
## Steps of an adoption
1. **Choose one integration**
Start with a useful case that is not critical. Read-only access is
best. See [Use cases](use-cases.md#overview-use-cases).
2. **Test on a test system**
Your TYPO3 partner sets up the access to the Suite. A developer then
installs the extension and creates an app. See the
[quick start](../developers.md#developers-quick-start).
3. **Review security and operations**
Examine [Your responsibilities](security.md#overview-security-operator) with the operators of the
installation.
4. **Define the rules for access**
Decide who can create apps, where you keep tokens, and how often you
review the list of apps.
5. **Start production use**
Start production use of the first integration. Then move the other
integrations, one at a time.
## Frequently asked questions
**Does it replace the TYPO3 backend?**
No. Editors continue to work in the backend. API Hub adds an API for
other applications. The same permissions apply.
**Does it make TYPO3 a headless CMS?**
No. It is for applications that use a backend user. It does not supply
content to anonymous website visitors.
**Can an application have more access than its user?**
No. The permissions of the backend user always apply. Scopes can only
reduce the access.
**Are AI assistants safe to use?**
An agent can use the REST API with a token. Scopes and permissions limit
it, as all other apps do. Start with read access. With write access, the
agent can change all data that its backend user can change.
More components of the TYPO3 Suite for AI agents are planned. They
will use the apps, tokens and scopes of API Hub, so the same control
applies.
**What happens when an employee leaves?**
Disable the backend user. The next request of each app that uses this
user then fails.
**Who has to maintain it?**
The TYPO3 Company supplies updates and is the manufacturer of the Suite
components. Your team or agency updates the installation and is
responsible for its extensions. Administrators manage apps in the
backend. They do not have to know how to develop software.
**What does it cost?**
API Hub is part of the TYPO3 Suite. TYPO3 CMS stays free. The
[page of the TYPO3 Suite](https://suite.typo3.com/) shows the current
offer and the prices.
**What changes with TYPO3 v15?**
The TYPO3 Company submitted this feature for integration in TYPO3
v15, and it will likely be part of it. A feature in the Core is part
of a regular release and is available to all users.