Batch define content types and attributes
Execute multiple content-type actions in a single request.
All actions are validated upfront before any execution begins. If any action has invalid fields, the entire batch is rejected with a 422 response and no actions are executed.
On domain errors (e.g., content type not found, permission denied), the
batch fails fast at the failing action. The error response includes an
"index" field (0-based) indicating which action caused the failure.
Actions before the failing index are committed; their results are not
returned. All verbs are idempotent — it is safe to re-send the entire
batch after fixing the error.
Request: {"actions": [<action>, <action>, ...]}
Each action object follows the same schema as the single-action
POST /api/v3/content-types endpoint. Maximum 50 actions per batch.
Response: {"results": [{"status": <code>, "data": <body|null>}, ...]}
Results are in the same order as the input actions. The data key is
null for 204 actions (deletes).
See POST /api/v3/content-types for available actions and their fields.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Batch request for content-type schema operations.
All actions are validated upfront before any execution begins.
1 - 50 elementsResponse
All actions executed successfully