Tradovate API Rate Limits: Handling 429 Responses
How CrossTrade reports broker-originated Tradovate 429 responses and where to find Tradovate's current rate-limit documentation.
Tradovate can apply broker-side rate limits to API requests. When that happens, CrossTrade reports the broker response so you can distinguish it from CrossTrade's own public API limit.
How CrossTrade reports Tradovate rate limits
When Tradovate returns an HTTP 429, CrossTrade passes the broker-originated response through as broker_rate_limited. If a wait interval is available, the response includes Retry-After. Honor that value before trying again.
What to do after a broker 429
- Wait for the full
Retry-Afterinterval before sending another request. - Check current orders and positions in Tradovate before resending a trading command whose outcome is uncertain.
- Manage urgent exposure directly in Tradovate if automation remains unavailable.
Tradovate's rate-limit documentation
Tradovate controls its rate limits and may change them. For current broker-specific mechanics and guidance, read Tradovate's public API FAQ and request-limit documentation.