Usage
JSON-RPC works by sending a request to a server implementing this protocol. The client in that case is typically software intending to call a single method of a remote system. Multiple input parameters can be passed to the remote method as an array or object, whereas the method itself can return multiple output data as well. (This depends on the implemented version.)
All transfer types are single objects, serialized using JSON.1
Request
A request is a call to a specific method provided by a remote system. It can contain three members:
method - A string with the name of the method to be invoked. Method names that begin with "rpc." are reserved for rpc-internal methods.params - An object or array of values to be passed as parameters to the defined method. This member may be omitted.id - A string or non-fractional number used to match the response with the request that it is replying to.2 This member may be omitted if no response should be returned.3
Response
The receiver of the request must reply with a valid response to all received requests. A response can contain the members mentioned below.
result - The data returned by the invoked method. If an error occurred while invoking the method, this member must not exist.4error - An error object if there was an error invoking the method, otherwise this member must not exist.5 The object must contain members code (integer) and message (string).6 An optional data member can contain further server-specific data. There are pre-defined error codes which follow those defined for XML-RPC.id - The id of the request it is responding to.
Since there are situations where no response is needed or even desired, notifications were introduced. A notification is similar to a request except for the id, which is not needed because no response will be returned. In this case the id property should be omitted (Version 2.0) or be null (Version 1.0).
Examples
In these examples, --> denotes data sent to a service (request), while <-- denotes data coming from a service. Although <-- is often called a response in client–server computing, depending on the JSON-RPC version it does not necessarily imply an answer to a request.
Version 2.0
Request and response:
--> {"jsonrpc": "2.0", "method": "subtract", "params": {"minuend": 42, "subtrahend": 23}, "id": 3}
<-- {"jsonrpc": "2.0", "result": 19, "id": 3}
Notification (no response, and no id):
--> {"jsonrpc": "2.0", "method": "update", "params": [1,2,3,4,5]}
Parse error:
--> {"jsonrpc": "2.0", "method": "subtract", "params":
<-- {"jsonrpc": "2.0", "error": {"code": -32700, "message": "Parse error"}, "id": null}
Invalid Request:
--> {"jsonrpc": "2.0", "method": 1, "params": "bar"}
<-- {"jsonrpc": "2.0", "error": {"code": -32600, "message": "Invalid Request"}, "id": null}
Method not found:
--> {"jsonrpc": "2.0", "method": "foobar", "id": 1}
<-- {"jsonrpc": "2.0", "error": {"code": -32601, "message": "Method not found"}, "id": 1}
Invalid params:
--> {"jsonrpc": "2.0", "method": "subtract", "params": {"minuend": 42}, "id": 2}
<-- {"jsonrpc": "2.0", "error": {"code": -32602, "message": "Invalid params", "data": "Missing required parameter: subtrahend"}, "id": 2}
Internal error:
--> {"jsonrpc": "2.0", "method": "getData", "params": [], "id": 4}
<-- {"jsonrpc": "2.0", "error": {"code": -32603, "message": "Internal error"}, "id": 4}
Batch request with errors:
--> [
{"jsonrpc": "2.0", "method": "subtract", "params": [42, 23], "id": 1},
{"jsonrpc": "2.0", "method": "foobar", "id": 2},
{"foo": "bar"}
]
<-- [
{"jsonrpc": "2.0", "result": 19, "id": 1},
{"jsonrpc": "2.0", "error": {"code": -32601, "message": "Method not found"}, "id": 2},
{"jsonrpc": "2.0", "error": {"code": -32600, "message": "Invalid Request"}, "id": null}
]
Version 1.1 (Working Draft)
