# Deriv API error: RateLimit

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/errors/deriv/rate-limit, 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.

The error, as text you can copy:

```
RateLimit
```

- Kind: API error code
- HTTP status: None recorded for this error
- API: [Deriv](https://openbrokerapi.com/brokers/deriv)
- Status: verified. Source: [developers.deriv.com](https://developers.deriv.com/llms/errors.md), checked 2026-10-09.

## What does RateLimit mean on the Deriv API?

Too many requests were sent. Deriv lists this among its common error codes.

## How do I fix RateLimit?

Slow down and retry after a pause. Deriv's API overview gives the concrete figures.

## Deriv limits behind this error

This is a rate or allowance error, so these are the limits recorded for Deriv, each with its scope and source. Pace your requests against them.

- Headline limit: 80/min per logged in user (REST)
  - Scope: user, REST
  - Sources conflict: [developers.deriv.com](https://developers.deriv.com/llms/api-overview.md) states 60 REST requests per minute per token, checked 2026-10-12. Deriv's API overview in the text form it publishes for AI tools gives REST 60 requests a minute per token, where its Limits page gives 80 a minute per logged in user. The same overview also gives 100 WebSocket requests a second per connection, 100 active subscriptions per connection and 5 concurrent WebSocket connections per user, none of which the Limits page mentions. Deriv's own pages disagree; the conflict is labelled, not resolved. Pace against 60.
  - Status: conflicting. Source: [developers.deriv.com](https://developers.deriv.com/docs/limits/), checked 2026-10-12.
  - Note: From the Limits page: REST is also capped at 300 a minute and 1,000 per ten minutes per IP address. WebSocket budgets, each shared by the calls in its row, a minute and an hour: proposal, proposal_open_contract, buy and sell 360 and 14,400; balance and statement 100 and 2,000; portfolio and profit table 30 and 1,500; all other calls 220 and 14,400. ping sits outside these budgets at 10 a second per connection.

## More on the Deriv API

- [All Deriv API error codes](https://openbrokerapi.com/errors/deriv)
- [Deriv API quickstart](https://openbrokerapi.com/brokers/deriv/quickstart): From credentials to a first call on a demo account, step by step.
- [Deriv API error codes](https://openbrokerapi.com/errors/deriv): 10 decoded, each with what it means, and the fix where the source gives one.
- [Deriv API endpoints](https://openbrokerapi.com/brokers/deriv/endpoints): 5 documented, each with its method, path, parameters and source.
- [Deriv messages](https://openbrokerapi.com/brokers/deriv/messages): 19 documented, each with its fields and source.
- [Deriv API page](https://openbrokerapi.com/brokers/deriv): The full record: access, authentication, limits and the source for each.

## Licence and how to cite

The records behind this page are all rights reserved. This file is the page itself, at its own address, in another format. It is not part of the CC BY 4.0 downloads listed at https://openbrokerapi.com/data. Quote from it with a link to the page.

Cite as: Deriv API error: RateLimit. Broker API Hub, https://openbrokerapi.com/errors/deriv/rate-limit, newest check 2026-10-09.

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.
