Dukascopy API rate limits
What is recorded about how fast you may call the Dukascopy API: 3 limit records, 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
One record per limit. The scope is part of the limit: a figure is only useful once you know whether it applies to a key, an account, a session or an address.
| Limit | Value | Scope | Source |
|---|---|---|---|
| Connection attempts a minute | 5 | Per IP address, per FIX server | dukascopy.comchecked |
| Open positions | 100 | FIX API. The guide does not say whether the count is per session or per account | dukascopy.comchecked |
| Orders a second | 16 | FIX API, orders only. The guide does not say whether the count is per session or per account | dukascopy.comchecked |
Rate limits, as the record words them
- Rate limits, as worded
FIX API: at most 16 orders a second, at most 100 open positions, and five connection attempts a minute per server for each IP address, per the FIX API Programming Guide, revision 8.8.1, re-read 12 Oct 2026. The JForex API pages opened state no request limit, which is not evidence that there is none.
Error codes that concern limits
Not recorded No decoded Dukascopy error names a rate limit yet.
Pacing and backoff, in general
This part is general advice and says nothing about Dukascopy 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 Dukascopy record
- Broker API rate limits compared
- HTTP 429 across broker APIs
- Rate limits for every broker and platform
- The fact register
Other brokers: Axi, Bitget, Capital.com, CMC Markets, Deriv, eToro, Exness, FOREX.com, FXCM, FxPro, IG, Interactive Brokers, OANDA, Pepperstone, Saxo, Swissquote, ThinkMarkets, Tickmill, Trading 212, XTB.