Skip to main content
When a request fails, the response body is still valid JSON-RPC: the result field is omitted and the error object contains a numeric code and a message. These codes are distinct from HTTP status codes (e.g. 401, 429, 504). Use the table below to interpret error.code in the response. For a successful HTTP 200, the response may still contain a JSON-RPC error (e.g. chain not supported). Always check for the presence of error in the response body.

​
Code → meaning and when it occurs

​
Standard JSON-RPC codes

  • -32700 and -32600 follow the JSON-RPC 2.0 spec for parse and invalid request errors.
  • -32602 is used for invalid chainId (invalid params).
  • -32603 is used for internal router errors.
  • -32xxx in the -32000 range are router-specific and documented above.

​
What to do when you see an error

  • -32700 / -32600: Fix the request payload (valid JSON, non-empty batch, required fields present).
  • -32602: Check the URL path; ensure chainId is present and correct. Use the API Reference (GET /chains) to see supported chain IDs.
  • -32001: Use a supported chain or contact us to request support for a new chain.
  • -32002: The method is not available for this chain; use a different method or chain.
  • -32003: Retry after a short backoff; cooldowns are temporary. See Request behavior: Cooldowns and rate limiting for details.
  • -32603 / -32000: Retry once; if it persists, contact support.
When contacting support, include the X-Batch-Id response header from the failed request if you have it. See Debugging.