Broker APIs with published rate limits
A rate limit is the number of requests an API accepts in a period before it refuses more. A published limit lets you pace a program before it is refused, instead of finding the ceiling by hitting it.
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.
Not recorded means this site holds no record. It does not mean the broker or platform lacks it. Rows are in name order, the order is not a ranking, and nothing here recommends a broker.
How each row is decided
Yes means the limits register holds at least one limit record for it: a figure or a wording, with its scope, read on the source shown. Where there is no limit record, the state is a row of the capability facts register if a sentence or an error record settles it. No means the record says no limit is published, which is not a statement that the API has no limit. Partial means a limit is documented for part of the API, or the record says limits exist and are served at runtime with no published figure. Any other sentence is printed and the state stays at not recorded.
- Yes
- A record on this site says so: a structured field, a record that exists, or a sentence in a record that was read and entered in the capability facts register, with the reason printed beside it. 13 of the 29 rows below.
- Partial
- A sentence in a record gives part of it: one route and not another, or a demo of the platform and not of the API. The reading is a row of the capability facts register, and the reason and the scope are printed beside it. 3 of the 29 rows below.
- No
- A record on this site says no: a structured field set to false, or a sentence in a record that says so, read and entered in the capability facts register. 5 of the 29 rows below.
- Not recorded
- This site holds no yes or no for it. That is a gap in this dataset. It is not a statement that the broker or platform lacks the capability. 8 of the 29 rows below.
4 of the rows rest on a record that is labelled unverified. Each says so beside its source.
Brokers
| Record | State | What the record holds | Source and date |
|---|---|---|---|
| Axi | Not recorded | The limits register holds no limit record. No state is taken from the record's sentence about rate limits: the capability facts register holds no reading of it as a yes, a partial or a no.
| UnverifiedTrading platforms, Axi UKchecked |
| Bitget | Yes | 6 limit records in the limits register, each with its scope. | bitgetlimited.github.iochecked |
| Capital.com | Yes | 1 limit record in the limits register, with its scope. | open-api.capital.comchecked |
| CMC Markets | Not recorded | The limits register holds no limit record. No state is taken from the record's sentence about rate limits: the capability facts register holds no reading of it as a yes, a partial or a no.
| CMC Connect connectivitychecked |
| Deriv | Yes | 1 limit record in the limits register, with its scope. | developers.deriv.comchecked |
| Dukascopy | Yes | 3 limit records in the limits register, each with its scope. | dukascopy.comchecked |
| eToro | Yes | 1 limit record in the limits register, with its scope. | api-portal.etoro.comchecked |
| Exness | Partial | The record says Exness publishes no figure and tells clients to read their limits at runtime from getRateLimits. Scope: No published figure. Limits are served at runtime. The limits register holds no limit record.
| Exness help centre: Exness APIchecked |
| FOREX.com / StoneX Trading (City Index) | Yes | 1 limit record in the limits register, with its scope. | docs.labs.gaincapital.comchecked |
| FXCM | No | The record says no rate limits are published, and that no REST API is listed to publish limits for. Not published is not the same as no limit.
| FXCM Socket REST API specchecked |
| FxPro | Not recorded | The limits register holds no limit record. No state is taken from the record's sentence about rate limits: the capability facts register holds no reading of it as a yes, a partial or a no.
| FxPro Prime brokeragechecked |
| IG | Yes | 5 limit records in the limits register, each with its scope. | labs.ig.comchecked |
| Interactive Brokers | Yes | 6 limit records in the limits register, each with its scope. | ibkrcampus.comchecked |
| OANDA | Yes | 1 limit record in the limits register, with its scope. | developer.oanda.comchecked |
| Pepperstone | Not recorded | The limits register holds no limit record. No state is taken from the record's sentence about rate limits: the capability facts register holds no reading of it as a yes, a partial or a no.
| UnverifiedPepperstone API tradingchecked |
| Saxo OpenAPI | Yes | 1 limit record in the limits register, with its scope. | developer.saxochecked |
| Swissquote | Not recorded | The limits register holds no limit record. No state is taken from the record's sentence about rate limits: the capability facts register holds no reading of it as a yes, a partial or a no.
| UnverifiedSwissquote institutional Forex APIschecked |
| ThinkMarkets | Not recorded | The limits register holds no limit record. No state is taken from the record's sentence about rate limits: the capability facts register holds no reading of it as a yes, a partial or a no.
| ThinkMarkets institutional saleschecked |
| Tickmill | Not recorded | The limits register holds no limit record. No state is taken from the record's sentence about rate limits: the capability facts register holds no reading of it as a yes, a partial or a no.
| Tickmill FAQ: FIX API connectionchecked |
| Trading 212 | Yes | 1 limit record in the limits register, with its scope. | docs.trading212.comchecked |
| XTB | No | The record says no published limits apply, because there is no live API. Not published is not the same as no limit.
| XTB help centre: Does XTB offer investment automation tools?checked |
Platform APIs
| Record | State | What the record holds | Source and date |
|---|---|---|---|
| cTrader Open API | Yes | 2 limit records in the limits register, each with its scope. | help.ctrader.comchecked |
| DXtrade APIs | Partial | An error record for the Push API says the vendor documents a rate limit on subscriptions with RequestType ALL, with a default of 1 per minute for each user and subscription name. Scope: Push API subscriptions only. No limit is recorded for the REST API. The limits register holds no limit record.
| demo.dx.tradechecked |
| Match-Trader Platform API | No | The record's sentence about rate limits is the two words Not published. Not published is not the same as no limit.
| Match-Trader Platform API PDF (2024)checked |
| MetaApi | Yes | 6 limit records in the limits register, each with its scope. | metaapi.cloudchecked |
| MetaCopier | Not recorded | The limits register holds no limit record. No state is taken from the record's sentence about rate limits: the capability facts register holds no reading of it as a yes, a partial or a no.
| UnverifiedMetaCopier documentation, REST APIchecked |
| MetaTrader 4 (MQL4) | No | The record's sentence about rate limits is the two words Not published. Not published is not the same as no limit.
| MQL4 Referencechecked |
| MetaTrader 5 (Python package and MQL5) | No | The record says no rate limit is published, and that the Python page states none. Not published is not the same as no limit.
| MetaTrader for Pythonchecked |
| TradeLocker API | Partial | The record says limits are per route and served at runtime by the /trade/config route, and that the documentation publishes no fixed figure. Scope: No published figure. The record adds that a request for more than 20,000 historical bars is rejected. The limits register holds no limit record.
| TradeLocker public API, getting startedchecked |
Where to go next
- Rate limits, broker by broker
- The full capability grid
- Which brokers have their own API
- Broker API documentation links
- Broker APIs with a demo or sandbox
- Broker APIs with streaming
- Broker APIs with authentication described
- Broker APIs with an official SDK or library
- Broker APIs with a Python library
- Broker APIs with an official MCP server
- Broker APIs with a community MCP server
- Brokers reachable through a platform API
- Broker APIs with endpoints documented here
- Broker APIs with error codes decoded here
- Broker APIs with an OpenAPI file on this site
- Broker APIs with a quickstart on this site
- Broker APIs with dated changes recorded
- Download the grid as JSON
How to cite this
Broker APIs with published rate limits. Broker API Hub, https://openbrokerapi.com/capabilities/rate-limits, newest check .
Where you rely on a single figure, cite the source and the checked date printed beside it as well.