How do I fix "Too Many Requests"?

Respect `Retry-After` and back off exponentially. Batch related calls and cache hot reads. Spread load across keys or raise your plan's rate limit. Use WebSocket subscriptions instead of polling where possible.

Too Many Requests (HTTP 429)

Last updated: June 20, 2026

At a glance

Error details
Property	Value
Code	HTTP 429
Message	Too Many Requests
Category	transport

Cause

Requests exceeded the endpoint's rate limit for your plan. The transport layer rejects with HTTP 429 before the JSON-RPC layer runs.

Solution

Respect `Retry-After` and back off exponentially.
Batch related calls and cache hot reads.
Spread load across keys or raise your plan's rate limit.
Use WebSocket subscriptions instead of polling where possible.

Example

{
  "body": "Too Many Requests",
  "status": 429
}

FAQ

Why does "Too Many Requests" happen?: Requests exceeded the endpoint's rate limit for your plan. The transport layer rejects with HTTP 429 before the JSON-RPC layer runs.
How do I fix "Too Many Requests"?: Respect `Retry-After` and back off exponentially. Batch related calls and cache hot reads. Spread load across keys or raise your plan's rate limit. Use WebSocket subscriptions instead of polling where possible.
What is RPC error HTTP 429?: HTTP 429 means: Too Many Requests. Requests exceeded the endpoint's rate limit for your plan. The transport layer rejects with HTTP 429 before the JSON-RPC layer runs.