Tradovate API limits

If you are running into Tradovate rate limiting, please enable "Use Market Orders for Followers" feature. This is the most effective way to reduce the impact of their limits.

Please note that these limits are outside of FutuCopy’s control, and any copier or application is subject to the same Tradovate-imposed limits.

We have also implemented our own limiter to reduce the likelihood of our servers from being limited by Tradovate. Our limiter does not apply to Pro Server subscribers.

FutuCopy Tradovate API limit policy

API Rate Limits

Tradovate enforces a rate limit on API requests to prevent overloading their servers. Every action FutuCopy performs on your behalf - placing, canceling, or modifying orders - requires an API request.

What is the limit?

Tradovate applies a dynamic rate limit to API requests. Rather than a single fixed cap, the limit adjusts based on their server traffic.

Explanation by a Tradovate engineer:

What happens when Tradovate starts limiting API requests?

When the soft rate limit is in effect, Tradovate issues a penalty ticket (also known as a "p-ticket"). During the penalty period:

• FutuCopy will resubmit failed call with Tradovate p-ticket and requested time delay.
• Your order modifications and placements on follower accounts will be slower.

Tips to reduce API usage

• Enable "Use Market Orders for Followers" feature.
• Avoid order modifications - adjusting stop losses or take profits will spike API calls.  
• Use Market orders instead of Limit orders - Limit orders that are frequently placed, modified, and canceled generate significantly more API requests than a single market order.
• Switch to Rithmic - use Rithmic accounts as your followers if your prop firm offers them. Rithmic does not have these limits and is more suitable for traders with many follower accounts.