Skip to content

JSON-RPC

Restorm offers two JSON-RPC 2.0 request types: the single call and the batch call.

Right-click in the tree ▸ Add ▸ JSON-RPC request (or JSON-RPC batch).

A JSON-RPC tab: the URL, the eth_blockNumber method, the request identifier, the parameters editor and the unwrapped response on the right

FieldRole
URLThe endpoint
MethodThe name of the method being called
ParametersRaw JSON: [...] for positional parameters, {...} for named ones
IdentifierThe request’s identifier; generated automatically if left empty
Notification modeOmits the identifier — the server must then return nothing
HeadersAdditional HTTP headers; Content-Type: application/json is added for you

In notification mode, the response panel says Notification sent: that is the expected behaviour, there is no response to show.

The JSON-RPC batch type carries a list of child calls, each with its method, its parameters, its identifier and its notification mode. Restorm sends the JSON-RPC array in a single HTTP call and matches responses to calls by their identifier — so you can see which response belongs to which call, even if the server returns them out of order.

An openrpc.json file creates one JSON-RPC request per method, under a Methods folder, with a sample params built from the content descriptors. See Importing OpenRPC.

Two targets: cURL and JavaScript (Fetch).