Skip to main content
Tradara enforces per-API-key rate limits at the gateway. JWT sessions are limited per user. The exact ceiling varies by endpoint class and your plan.
Published rate-limit values are indicative. Your contract may grant higher limits. Production limits will be finalised before GA — track this page for updates.

​
Limit classes

Streaming connections do not consume request quota once established, but message backpressure can still terminate slow consumers — see Reconnection & backpressure.

​
Response headers

Every response includes:

​
Handling 429 Too Many Requests

Recommended strategy:
  1. Honour Retry-After.
  2. Use exponential backoff with jitter for retries beyond the first.
  3. Coalesce reads — prefer the WebSocket stream over polling fills or positions.
  4. Batch order operations where possible (cancel-all, flatten, close-all instead of N cancels).
  5. Cache instrument metadata and account references locally.

​
Order-flow guidance

For high-frequency trading patterns:
  • Use POST /v1/orders/groups for bracket strategies to reduce write count.
  • Subscribe to the firm WebSocket for state updates instead of polling.
  • Place orders with deterministic client_order_id so retries are cheap and traceable.

​
Asking for a higher limit

Reach out to your Tradara account contact with: peak QPS observed, target QPS, the endpoint class, and the use case. Production-grade firms typically operate well below class ceilings — if you are hitting them, double-check that you are not polling endpoints that have a WebSocket equivalent.