TradeLocker API rate limits
What is recorded about how fast you may call the TradeLocker API: no per limit record yet, the wording from the record and no related error code yet.
Risk warning: CFDs and spread bets are complex instruments and come with a high risk of losing money rapidly due to leverage. You can lose money on these products, and each provider publishes its own loss figure under FCA rules. You should consider whether you understand how they work and whether you can afford to take the high risk of losing your money. Automated and API trading can amplify losses through bugs, connectivity failures and runaway orders.
Recorded limits
Not recorded No separate limit record is held for TradeLocker API yet. That is a gap in this dataset, not a statement that there is no limit.
Rate limits, as the record words them
- Rate limits, as worded
Per route limits only, served at runtime by the /trade/config route as a number of requests per interval of seconds or minutes. The documentation publishes no fixed figure and gives 2 requests a second only as an example of the form. A tl-developer-api-key header, issued through the TradeLocker Developer Program, gets less restrictive limits. Separately, a request for historical bars is rejected if it would return more than 20,000 bars.
TradeLocker public API, getting startedchecked TradeLocker public API, index of pageschecked
Error codes that concern limits
Not recorded No decoded TradeLocker API error names a rate limit yet. All TradeLocker API errors.
Pacing and backoff, in general
This part is general advice and says nothing about TradeLocker API in particular. The figures that apply are the recorded ones above, and the provider's own documentation is the authority.
Pace before you are refused. Work out the gap between requests that keeps you under the limit, then leave a margin, because a limit counted by a provider's clock will not line up exactly with yours. Spread calls evenly: a burst at the start of each window is the usual way to hit a limit while staying under it on average. The rate limit calculator checks a polling plan against a limit and gives the shortest interval that fits.
When a request is refused for rate, stop sending and wait. Double the wait after each refusal in a row, add a small random amount so that several programs do not retry together, and cap the number of attempts. If the reply names how long to wait, use that figure in place of your own.
Take extra care with dealing requests. A refused or unanswered order may or may not have gone through, so check the state of the order before you send it again. Cache what does not change, such as instrument details and history you have already downloaded, and prefer a stream to polling where one is offered.
Where to go next
- The full TradeLocker API record
- TradeLocker API endpoints
- All TradeLocker API error codes
- Broker API rate limits compared
- HTTP 429 across broker APIs
- Rate limits for every broker and platform
- The fact register
Other platforms: cTrader, DXtrade, Match-Trader, MetaApi, MetaCopier, MetaTrader 4, MetaTrader 5.