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

CodeMeaning
400Bad Request -- Your request is invalid. Double-check your JSON-RPC body.
429Too Many Requests -- You've exceeded your qps rate limit. Get in touch with us if you need to increase your rate limits.
500Internal 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

CodeMessageDescription
-32700Parse errorInvalid JSON was received by the server. An error occurred on the server while parsing the JSON text.
-32600Invalid RequestThe JSON sent is not a valid Request object.
-32601Method not foundThe method does not exist / is not available.
-32602Invalid paramsInvalid method parameter(s).
-32603Internal errorInternal JSON-RPC error.
-32000 to -32099Server errorReserved 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
}