# MetaApi API rate limits Independent and unofficial. Not affiliated with or endorsed by any broker or platform named here. Educational only: nothing here is advice, and nothing here recommends a broker or a trade. This is the markdown version of https://openbrokerapi.com/platforms/metaapi/rate-limits, written from the same records as that page. 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. What is recorded about how fast you may call the MetaApi API: 6 limit records, the wording from the record and no related error code yet. - Newest check: 2026-10-12 ## 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. - CPU credits per account: 5,000 CPU credits per 10 seconds - Scope: Per MetaTrader account. REST and RPC calls only - Status: verified. Source: [metaapi.cloud](https://metaapi.cloud/docs/client/rateLimiting/), checked 2026-10-12. - Note: The window is 10 seconds, which a single unit cannot state, so the figure stays as wording. - CPU credits an hour, per application: 18,000 credits per hour - Scope: Per application, multiplied by the number of accounts deployed to MetaApi. REST and RPC calls only, counted in CPU credits and not in requests - Status: verified. Source: [metaapi.cloud](https://metaapi.cloud/docs/client/rateLimiting/), checked 2026-10-12. - Note: Also 43,200 credits per 6 hours. - CPU credits a minute, per application: 6,000 credits per minute - Scope: Per application, multiplied by the number of accounts deployed to MetaApi. REST and RPC calls only, counted in CPU credits and not in requests - Status: verified. Source: [metaapi.cloud](https://metaapi.cloud/docs/client/rateLimiting/), checked 2026-10-12. - CPU credits a second, per application: 1,000 credits per second - Scope: Per application, multiplied by the number of accounts deployed to MetaApi. REST and RPC calls only, counted in CPU credits and not in requests - Status: verified. Source: [metaapi.cloud](https://metaapi.cloud/docs/client/rateLimiting/), checked 2026-10-12. - Note: Most read calls cost 50 credits, a trade costs 10 and listing symbols costs 500. Streaming uses no CPU credits. HTTP 429 with a recommended retry time on breach. - Concurrent historical market data requests: 5 concurrent requests - Scope: Per MetaTrader account, historical market data API only - Status: verified. Source: [metaapi.cloud](https://metaapi.cloud/docs/client/rateLimiting/), checked 2026-10-12. - CPU credits a second, per server: 2,000 credits per second - Scope: Per shared front end server. REST and RPC calls only, counted in CPU credits and not in requests - Status: verified. Source: [metaapi.cloud](https://metaapi.cloud/docs/client/rateLimiting/), checked 2026-10-12. - Note: Also 18,000 a minute, 180,000 an hour and 432,000 per 6 hours on one server. The page says a different client-id header selects a different server. ## Rate limits, as the record words them - Rate limits, as worded: Limits are counted in CPU credits, not requests. Each REST or RPC call costs credits: most reads cost 50, a trade costs 10 and listing symbols costs 500. An application gets 1,000 credits a second, 6,000 a minute, 18,000 an hour and 43,200 per 6 hours, each multiplied by the number of accounts it has deployed. A single shared front end server allows 2,000 credits a second, a single account allows 5,000 credits per 10 seconds, and historical market data allows 5 concurrent requests per account. Going over returns HTTP 429 with a recommended retry time in the error. - Status: verified. Source: [MetaApi documentation, rate limiting](https://metaapi.cloud/docs/client/rateLimiting/), checked 2026-10-12. ## Error codes that concern limits Not recorded: no decoded MetaApi error names a rate limit yet. ## Pacing and backoff, in general This part is general advice and says nothing about MetaApi 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 at https://openbrokerapi.com/tools/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 MetaApi record](https://openbrokerapi.com/platforms/metaapi) - [Rate limits for every broker and platform](https://openbrokerapi.com/rate-limits) - [The fact register](https://openbrokerapi.com/facts) ## Licence and how to cite The limit records on this page come from the limits register, which is CC BY 4.0 (https://openbrokerapi.com/data/limits.json). Everything else on it comes from records that are all rights reserved. This file is the page itself, at its own address, in another format, and it is not part of the CC BY 4.0 downloads listed at https://openbrokerapi.com/data. Cite as: MetaApi API rate limits. Broker API Hub, https://openbrokerapi.com/platforms/metaapi/rate-limits, newest check 2026-10-12. Where you rely on a single figure, cite the source and the checked date printed beside it as well. Where this page and a broker's own documentation differ, the documentation wins.