Rate Limits
Overview
This API enforces throttling to ensure reliable and predictable access. Requests are executed synchronously and queued when multiple arrive.
Throttling Behavior
- Requests are processed synchronously
- Additional requests are queued until processing becomes available.
- If processing and queue capacity reaches its limits, new requests are rejected.
Rejections
When the system cannot accept more requests into the queue, the API responds with:
- HTTP 429 Too Many Requests
Client Integration Guidelines
- Synchronous Execution: Always wait for a response before sending the next request.
- Rate Limiting: Pace your requests to avoid hitting queue limits.
- Handling 429: Implement retry logic with a delay or exponential backoff.