Skip to content
Docs

Rate limits

The API applies a request limit to protect the platform.

The limit

Section titled “The limit”
  • 1500 requests per minute, per IP address
  • The window is 60 seconds

This limit is generous for normal usage, including polling submissions and renders. If you run many processes from the same IP, spread your calls out over time.

When the limit is hit

Section titled “When the limit is hit”

When you exceed the limit, the API responds with:

  • Status 429 Too Many Requests
  • A Retry-After header with the number of seconds you should wait
  • Body: { "code": "RATE_LIMIT_EXCEEDED" }
HTTP/1.1 429 Too Many Requests
Retry-After: 60


{ "code": "RATE_LIMIT_EXCEEDED" }

How to handle it

Section titled “How to handle it”
  • Respect the Retry-After: wait the indicated number of seconds before trying again
  • Use backoff for repeated calls, instead of retrying immediately
  • Space out polling: when tracking a submission or a render, check at intervals of a few seconds instead of in a tight loop