Error Codes
This page is a reference on Node error codes which include both HTTP and JSON-RPC errors.
HTTP Error Codes
Coinbase Node returns standard HTTP error codes before JSON-RPC error codes, as establishing the HTTP connection is a first step to calling our APIs. Another way to track your successful/failed calls is on the project dashboard.
tip
200-level HTTP responses indicate success, 400-level indicate user error, and 500-level indicate a server-level error. You can see this on your project dashboard.
| Code | Message |
|---|---|
| 200 | Request was successful |
| 400 | Request is invalid. Try checking your JSON-RPC request body. |
| 401 | Request is unauthorized. Ensure your API credentials are properly provisioned and passed. |
| 403 | Request is forbidden. We understand your request, but you may have hit your rate limit. |
| 405 | Request method is not allowed. Check the API reference to verify you are calling a valid method. |
| 429 | Too many requests. You exceeded your plan's allotted amount. Check your project dashboard for usage metrics or your plan’s request capacity. |
| 500 | Internal Server Error. Contact us as we are unable to process your request. |
JSON-RPC Error Codes
JSON-RPC errors are thrown by our nodes. So while the request succeeded, your request method, format, or network may have the error.
| Code | Message | Description |
|---|---|---|
| -32700 | Parse error | Invalid JSON 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 parameter(s) |
| -32603 | Internal error | Internal JSON-RPC error |
| -32000 to -32099 | Server error | Reserved for implementation-defined server-errors |