/api/v1/, and the API is designed to be predictable: consistent resource structures, a unified error envelope, and standard pagination across every list endpoint.
Base URL
All API requests go tohttps://hub.terminus.app, and every endpoint is versioned under /api/v1/.
If your team is on a dedicated Terminus Hub deployment, use its host in place of
hub.terminus.app.Authentication
Every request to the Public API must include a valid API key in theAuthorization header using the Bearer scheme:
thub_ so they are easy to identify. See the Authentication page for full details on creating keys, using them in code, and handling auth errors.
Request Format
All requests must include theContent-Type: application/json header when sending a request body (e.g., POST requests). Responses are always returned as JSON.
Rate Limiting
Each API key may make up to 100 requests per minute. When you exceed the limit, the API returns429 with a rate_limit_error and a Retry-After header telling you how long to wait. Implement exponential back-off to handle these gracefully. See Pagination & Errors for the headers and full error schema.
Example Request
The following example fetches the list of Workspaces your API key has access to. It is a good first request to verify that your key is working correctly.Available Resources
The Public API exposes four resource groups. Use the cards below to navigate to each section.Workspaces
List and retrieve Workspaces, the top-level containers that group your submissions and records.
Governance Models
Browse the Governance Models available in your hub, including their names and descriptions.
Submissions
Create new Submissions and list existing ones filtered by Workspace and Taxonomy.
Records
Query individual Records within a Workspace, including their status and attached data payload.