Rate Limits and Versioning

300 requests per minute per key, how to handle 429s, and the additive-only versioning promise.

Rate limit

Each API key can make 300 requests per minute. Over the limit, the API returns 429 with the code rate_limited and a Retry-After header. Wait that long before retrying.

To stay under the limit:

  • Poll runs at a modest interval rather than in a tight loop.
  • Use pageSize up to 100 when listing, so you need fewer pages.
  • Give separate pipelines separate keys, so one busy job does not slow another.

Versioning

Paths start with the version, /v1. Within a version, changes are additive only: new fields and new operations are added, and existing ones are never removed or renamed.

Build your client to ignore fields it does not recognize, so additions do not break it. API changes are announced in the changelog.


Did this page help you?