Base URL and versioning
All REST requests go to a versioned base path:v1) is in the path. We add fields and endpoints without bumping the version; a breaking change would ship under a new version path so your integration keeps working.
Requests and responses
Requests and responses are JSON (Content-Type: application/json). Send a JSON body on POST, PATCH, and PUT; send query parameters on GET.
A single-resource response returns that resource directly:
Pagination
List endpoints are cursor-paginated. Passlimit to set the page size and cursor to fetch the next page:
data and returns paging metadata in page:
nextCursor value back as the cursor parameter. When hasMore is false, nextCursor is null and you’ve reached the end.
Errors
Successful requests return2xx. Errors return the matching HTTP status and an RFC 7807 problem document (Content-Type: application/problem+json):
Branch your error handling on the
code field (stable) rather than the human-readable title or detail.
Service status
GET /v1/status is an unauthenticated health check, and GET /v1/openapi.json returns the full OpenAPI document that powers this reference.