API reference
Every endpoint, with its request and response schema, generated from the controllers.
Every endpoint in this reference is generated from the backend controllers on each build, so it always matches the deployed API.
Authentication
Send one credential with every request, in either header:
Authorization: Bearer <token>, where the token is an API key (crtk_live_…) or an OAuth access token (crtk_oauth_…).X-Api-Key: <key>, where the key is an API key.
You do not send scopes. They come from the credential: an API key has the scopes chosen when it was created, and an OAuth access token has the scopes granted when your app was authorized. A request acts as the member who created the key or authorized the app.
Open any endpoint, paste your API key or access token into the Bearer token field, and send the request. The token is saved only in this browser, and this site forwards the request to the API.
Errors
Every error response has the same JSON body. status repeats the HTTP status code and message says what went wrong. Some errors also set code, a stable reason, and data, extra detail. See Errors for how to handle them.
Import the spec
Get the raw OpenAPI 3.0 spec from openapi.json and import it into Postman, Insomnia, or any other OpenAPI tool. It lists the same 67 path(s) as this reference and declares both authentication headers.
Start with the quickstart if you have not created a key yet.