API reference
API reference
Twelfth’s public API is deliberately small and read-only. Each endpoint has a focused page with generated request, response, schema, authentication, and error details.
People can browse one page per endpoint. Software and agents should read the canonical OpenAPI 3.1 JSON directly. The info.version value required by OpenAPI describes the contract document; Twelfth does not put version numbers in URL paths.
For agents
Use these sources in order:
- OpenAPI JSON for operations, schemas, authentication and stable error shapes.
- Developer API for credential choice and the boundary between public and internal routes.
- API compatibility before generating a client or proposing a contract change.
llms.txt,llms-full.txtor the OKF bundle for the wider product and workflow context behind an operation.
Do not infer customer API support from browser /api/... routes or examples in application code. If an operation is absent from the public OpenAPI document, it is not a supported external HTTP operation.
Endpoints
Read the workspace identity and its timezone, currency, and country defaults.
Read up to 100 open, unsnoozed tasks across the workspace, ordered by due date.
Need another read?
Tell us the resource, fields, workflow, and expected request volume. Requests help decide which small, stable endpoint comes next.