Skip to main content

Limits per key

The limits apply per API key, in a sliding window of 1 minute.

Headers

Every authenticated response carries: Every response, success or error, carries X-Request-Id. Quote this value when you contact support.

When you get a 429

There are two cases, both with Retry-After:
  • rate_limited: the key exceeded the per-minute limit.
  • concurrency_limit: the workspace already has too many pre-tests in progress (about 10 created through the API). Wait for one to finish.
Wait the Retry-After interval and try again. If it is a creation, reuse the same Idempotency-Key (Idempotency).

Good practices

  • Poll the status of a pre-test every 10 seconds or more, not in a tight loop.
  • For many pre-tests, use the list (GET /pretests) instead of querying them one by one.
  • Spread creations over time: the write limit is 60 per minute.