Skip to main content

Error response format

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32602,
    "message": "Invalid params"
  }
}

Standard JSON-RPC errors

CodeNameDescription
-32700Parse errorInvalid JSON in request body
-32600Invalid requestMissing required JSON-RPC fields
-32601Method not foundMethod does not exist or is unsupported
-32602Invalid paramsWrong parameter types or count
-32603Internal errorServer-side processing error

EVM-specific errors

CodeNameDescription
-32000Call exceptionContract call failed (reverted, out of gas, etc.)
-32003Transaction rejectedTransaction validation failed
3Execution revertedContract execution reverted with reason

Edge RPC normalized errors

Edge RPC normalizes errors from upstream providers to consistent codes:
CodeNameDescription
-32005Rate limit exceededToo many requests
-32012Range too largeBlock range in eth_getLogs too large
-32014Missing dataBlock, transaction, or state not found
-32015Node timeoutUpstream node timed out
-32016UnauthorizedInvalid or missing authentication