Kraken Rate Limits
Kraken enforces request-rate policies separately per surface. The Spot REST private API uses a per-key "API counter" that increments on every call and decays over time at a tier-dependent rate; the counter's maximum value determines burst capacity, and the per-second decay determines steady-state throughput. The Spot REST public API is throttled per IP. Spot WebSocket subscriptions are rate-limited per connection (token-bucket on subscribe / unsubscribe / trading calls). Kraken Futures uses a separate per-key counter with its own ceiling and decay. Institutional / colocation clients can negotiate raised limits. All over-limit responses use HTTP 429 (REST) or a WebSocket `EAPI:Rate limit exceeded` error frame.
Kraken Rate Limits is the machine-readable rate-limit profile for Kraken on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 16 rate-limit definitions, measuring requests_per_minute, api_counter, trade_counter, requests_per_second, and concurrent_requests.
The profile also includes 9 backoff/retry policies defined and response codes documented for throttled, unauthorized, serverBusy, and websocketRateLimit.
Tagged areas include Rate Limiting, Cryptocurrency, Exchange, API Counter, and WebSocket.
Limits
Policies
Sources
- https://support.kraken.com/articles/206548367-what-are-the-api-rate-limits
- https://docs.kraken.com/api/docs/guides/spot-rest-ratelimits
- https://docs.kraken.com/api/docs/guides/spot-ws-ratelimits
- https://docs.kraken.com/api/docs/guides/futures-api-ratelimits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.