Request schema
{
"type": "object",
"properties": {
"method": {
"type": "string",
"description": "JSON-RPC read method, e.g. query",
"examples": [
"EXPERIMENTAL_changes",
"EXPERIMENTAL_changes_in_block",
"EXPERIMENTAL_congestion_level",
"EXPERIMENTAL_genesis_config",
"EXPERIMENTAL_light_client_block_proof",
"EXPERIMENTAL_light_client_proof",
"EXPERIMENTAL_maintenance_windows",
"EXPERIMENTAL_protocol_config",
"EXPERIMENTAL_receipt",
"EXPERIMENTAL_split_storage_info",
"EXPERIMENTAL_tx_status",
"EXPERIMENTAL_validators_ordered",
"block",
"changes",
"chunk",
"client_config",
"gas_price",
"genesis_config",
"health",
"light_client_proof",
"maintenance_windows",
"network_info",
"next_light_client_block",
"query",
"status",
"tx",
"validators"
]
},
"params": {
"description": "Parameters per the NEAR RPC spec (positional or named)"
}
},
"required": [
"method"
]
}
Response schema
{
"type": "object",
"description": "JSON-RPC 2.0 response envelope. Exactly one of `result` or `error` is present. `result` takes the shape the called method defines per the NEAR RPC specification; NEAR conventionally echoes a string id.",
"properties": {
"jsonrpc": {
"type": "string",
"description": "The protocol version, always \"2.0\""
},
"id": {
"type": [
"string",
"number",
"null"
],
"description": "The request id, echoed back"
},
"result": {
"description": "The method's result, in the shape the called method defines. Present when the call succeeded; absent when `error` is."
},
"error": {
"type": "object",
"description": "Present instead of `result` when the call failed",
"properties": {
"code": {
"type": "integer",
"description": "A JSON-RPC 2.0 error code"
},
"message": {
"type": "string"
},
"data": {
"description": "Method-specific detail, when the node supplies it"
}
}
}
},
"examples": [
{
"jsonrpc": "2.0",
"id": "dontcare",
"result": {
"gas_price": "100000000"
}
}
]
}