Error Codes
Learn how the Tatum RPC Gateway handles errors using JSON-RPC 2.0 and custom error codes that identify validation issues, rate limits, and upstream node failures.
The Tatum RPC Gateway follows the JSON-RPC 2.0 specification
When a request fails, the Gateway returns structured error codes that help determine whether the issue originates from:
- the client request,
- the Gateway middleware, or
- the upstream blockchain node.
Tatum Gateway Error Codes
Tatum extends the JSON-RPC standard with custom error codes to clearly distinguish between validation issues, rate limits, middleware failures, and upstream node problems.
Code | Message | Description |
|---|---|---|
-16401 |
| The request format or structure was invalid. Verify JSON syntax and required fields. |
-16402 |
| One or more items in a batch request failed validation. |
-16405 |
| The requested RPC method is not supported or not enabled for the selected blockchain. |
-16412 |
| The request payload failed validation due to exceeding permitted limits. |
-16429 |
| You have exceeded your rate limit. Reduce the request frequency or upgrade your plan. |
-16500 |
| The upstream node returned a malformed or unexpected response. |
-16502 |
| The upstream node’s response body was incomplete, missing fields, or not parsable. |
-16503 |
| No healthy node was available to serve the request. The Gateway could not route the call. |
-16504 |
| Internal middleware or infrastructure failure. Retry or check Tatum Status. |
Standard JSON-RPC Error Codes
| Code | Message | Description |
|---|---|---|
| -32700 | Parse error | Invalid JSON was received by the server. |
| -32600 | Invalid Request | The JSON sent is not a valid Request object. |
| -32601 | Method not found | The method does not exist or is not available. |
| -32602 | Invalid params | Invalid method parameters. |
| -32603 | Internal error | Internal JSON-RPC error. |
| -32000 to -32099 | Server error | Reserved for implementation-defined server errors. |
Updated about 5 hours ago