Issue Feature Under Review Quiet

#111046Introduce Action API as typed RPC layer for remote systems

Benjamin Franzke 10/14/26, 10:56 updated 11/06/26, 10:12

Description

TYPO3 lacks a uniform, machine-readable way for remote systems (JavaScript clients, integrations, AI agents) to invoke backend functionality. AJAX routes and custom controllers each do their own argument parsing, validation, permission checks and response formatting, and none of them is self-describing.

Introduce an Action API: service methods marked with a new #[AsAction] attribute become RPC actions. Their input and output JSON Schema is derived from the method signature (native and PHPDoc types) at container compile time.

  • Arguments and results are validated against the derived schema
  • An ActionType (fetch, create, replace, update, delete, dispatch) maps each action to an HTTP verb
  • Access is restricted by scopes (content:read, content:write, extensible via ScopeInterface)
  • In the backend, actions are exposed as JSON endpoints below /typo3/api/, authenticated with a user-bound bearer token, plus a small JavaScript client module

The JSON Schema descriptions are the basis for generating an OpenAPI 3.1 document and exposing actions via MCP in follow-up changes

Reviews 2

History 19

  1. Gerrit Code Review pushed patch set 55 for main to change 91563 status New Under Review <span data-processor="relativetime" data-value="2026-10-14T11:03:23+00:00" > 10/14/26, 11:03 </span>