Rate limits and pagination

Preview, not available yet

This describes the v1 preview. The API is switched off in every environment until we announce it in the changelog.

Rate limits

Each client can make 600 requests per minute. Above that, the API answers 429 with the error code rate_limited and a Retry-After header with the number of seconds to wait:

HTTP/1.1 429 Too Many Requests
Retry-After: 12
Content-Type: application/json

{ "code": "rate_limited", "correlation_id": "…", "retryable": true, "field_errors": [] }

Wait at least Retry-After seconds before you send the next request. Reuse your access token for its 15 minutes instead of asking for a new one before every call; token requests count too.

Each organization can have at most 5 clients that are not revoked.

Pagination

v1 has no list operations yet. When lists arrive (from v1.1), they will return one page at a time:

{ "items": [], "next_cursor": "c2ltYmxpYS1leGFtcGxl" }

• Pass next_cursor as cursor to get the next page. next_cursor is null on the last page.
• Use limit to choose the page size: 25 by default, at most 100.
• Cursors are opaque. Do not build or change them. A cursor only works for the client and organization that received it.

The exact parameter names will be confirmed in the contract for v1.1 and announced in the changelog.