Skip to main content
Every authenticated Platform API endpoint (/api/v1/platform/* and /api/v1beta/platform/*) is subject to a per-organization rate limit. Limits are counted separately for each organization, so one organization’s traffic never affects another.
Path versions differ by resource. The limit applies the same way regardless of version. See Versions and compatibility.

Limits

The limit uses a fixed 1-second window. The counter resets at the start of every second.

Response headers

Every rate-limited response includes headers describing the state of the current window.

Limit exceeded response

When you exceed the limit, the API returns 429 Too Many Requests with the following body.
Wait for the number of seconds in the Retry-After header, then send the request again.

Staying within the limit

1

Check remaining requests

Use the X-RateLimit-Remaining value in each response to see how many requests you can still send in the current window.
2

Handle 429 responses

When you receive a 429, wait for the seconds in the Retry-After header and retry.
3

Spread out bulk work

If you need to send many requests, space them out to stay within the per-second limit.
When you need to process many items at once, such as bulk creation, use the bulk endpoints instead of sending one request per item to reduce the number of requests.
For billing, see Credits.