DXtrade API rate limits
What is recorded about how fast you may call the DXtrade API: no per limit record yet, the wording from the record and 2 related error codes.
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 DXtrade APIs 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
Unverified. The DXtrade developer portal, where a limit would be written, returned only a page title without scripts on 12 Oct 2026. Devexperts' APIs page and its traders FAQ, both opened that day, state no limit. That is not evidence that there is none, and the FAQ says each broker decides whether to open the API at all.
UnverifiedDXtrade traders FAQchecked UnverifiedDXtrade APIschecked
Error codes that concern limits
These are the decoded DXtrade APIs errors whose code or meaning names a rate limit, an allowance or throttling. Each row links to the full meaning and the fix.
| Code | HTTP status | Meaning, first sentence | Source |
|---|---|---|---|
| 429 Too Many Requests | 429 | DXtrade REST API: The user sent too many requests in a given amount of time. | demo.dx.tradechecked |
| Reject 429 Too Many Requests | Not recorded | DXtrade Push API: the vendor says that if the access rate is exceeded, a Reject message "429 Too Many Requests" is sent. | demo.dx.tradechecked |
Pacing and backoff, in general
This part is general advice and says nothing about DXtrade APIs 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 DXtrade APIs record
- DXtrade APIs endpoints
- All DXtrade APIs 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, Match-Trader, MetaApi, MetaCopier, MetaTrader 4, MetaTrader 5, TradeLocker.