Error Reference
Learn about the standard JSON-RPC error codes and Shinami's custom error codes.
In addition to the standard JSON-RPC error codes, Shinami will return the following status codes for HTTP requests:
HTTP Status Codes
Code | Meaning |
---|---|
400 | Bad Request -- Your request is invalid. Double-check your JSON-RPC body. |
429 | Too Many Requests -- You've exceeded your qps rate limit. Get in touch with us if you need to increase your rate limits. |
500 | Internal Server Error -- We're unable to process your request right now. Get in touch with us if you see this. |
Example Response
// Example 429 Error
{
"jsonrpc": "2.0",
"error": {
"code": 429,
"message": "rate limit exceeded"
},
"id": 1
}
For JSON-RPC specific errors, Shinami returns a 200
with the JSON-RPC error in the JSON response.
JSON-RPC Error Codes
Code | Message | Description |
---|---|---|
-32700 | Parse error | Invalid JSON was received by the server. An error occurred on the server while parsing the JSON text. |
-32600 | Invalid Request | The JSON sent is not a valid Request object. |
-32601 | Method not found | The method does not exist / 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. |
Example Response
{
"jsonrpc":"2.0",
"error":{
"code":-32602,
"message": "byte deserialization failed, cause by: Odd number of digits"
},
"id":1
}
Updated about 1 year ago