RPC
Introduction
This is not a standard specification. If you need it, go to the JSON-RPC Working Group Website.
Requests
id
jsonrpc
method
params
Responses
error
error.code
A Number that indicates the error type that occurred.
This MUST be an integer.The error codes from and including -32768 to -32000 are reserved for pre-defined errors. Any code within this range, but not defined explicitly below is reserved for future use. The error codes are nearly the same as those suggested for XML-RPC at the following url: http://xmlrpc-epi.sourceforge.net/specs/rfc.fault_codes.php
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 …-32099 |
Server error | Reserved for implementation-defined server-errors. |
error.data
A Primitive or Structured value that contains additional information about the error.
This may be omitted.
The value of this member is defined by the Server (e.g. detailed error information, nested errors etc.).
error.message
A String providing a short description of the error.
The message SHOULD be limited to a concise single sentence.
id
jsonrpc
result
References and Further Reading
-
JSON-RPC 2.0 Specification.
JSON-RPC Working
Group.
Date Published: . Date Updated: . Date Retrieved: .
-
Contributors of Wikipedia: JSON-RPC.
Wikipedia -
The Free Encyclopedia.
Date Modifed: . Date Retrieved: .