API Rate Limit Question

[lukectv56]

I am creating a high frequency trading algorithm and there is no information regarding API rate limit / minute on the API documentation. Anyone have numbers regarding the API rate limit?

Thanks.

[God]

There’s a mention of rate limits in the doc:

Tradovate API

and these two posts:

Understanding Tradovate's Rate Limits

Tradovate limits the API requests that can be made on a second, minute, and hourly basis. As soon as a cap is reached, the server will begin responding with 429: Too Many Requests. Consumers of the API should be aware of these limitations. Useful links in understanding Tradovate’s rate limits: https://api.tradovate.com/#section/Request-rate-limits-and-time-penalty

Details requested on rate limiting threshold for market data requests

I’m finding that my project is getting hit with the rate limiter quite often when using the getChart request. I was wondering if you could please provide more specifics around the thresholds here for market data? Is there a way to increase the limitations if needed?

However, the exact amount isn’t clarified exactly. Seems like the smallest request time frame that the API permits is every second. Maybe @BWeis or @Alexander could clarify.

[lukectv56]

Yeah I’m looking for the exact amount. Hopefully Alexander can get back to this post as he has abandoned my discussion post regarding 404 errors when submitting startorderstrategy via API…

[Alexander]

The official API FAQ has these answers - if you’re looking for exact values I’m sorry to say you won’t find them. That’s because we don’t have exact values for rate limits. These are subject to constant change based on current traffic and other factors. Having hard-coded values increases the possibility of certain risks as well, such as DDoS attacks, so this is actually an added defensive measure. You can find more details in the link below.

tradovate/example-api-faq/blob/main/docs/HowDoesTradovateLimitRequestsAndData.md

[lukectv56]

So what is the approximate minimum rate limit that we won’t have any problems?

[Alexander]

Even if you break into the rate limits, for most operations it’s as simple as waiting p-time seconds and resending your requests with the original body plus the p-ticket field added on. If you’re placing orders or modifying orders at a rate fast enough to get this response, you’ll likely only have to deal with this scenario. The point is to make sure your calling code accounts for this response and you’ll be fine.

Regarding those 404s, please send me some code (privately) and we can work through it together. I’m still not sure why you’re getting those 404s but usually it’s an incorrect string somewhere, the wrong endpoint, an incorrect base URL, or using the wrong type of websocket (there are three socket services we offer, each requiring a different base URL - standard real-time, market data, and market replay).

[lukectv56]

@Alexander

Regarding those 404s, please send me some code (privately) and we can work through it together. I’m still not sure why you’re getting those 404s but usually it’s an incorrect string somewhere, the wrong endpoint, an incorrect base URL, or using the wrong type of websocket (there are three socket services we offer, each requiring a different base URL - standard real-time, market data, and market replay).

I’ll shoot you a pm of the code that returns 404.