JSON-RPC Tester

Construct, test, and debug JSON-RPC 2.0 requests with response inspector and history.

About JSON-RPC Tester — Detailed Guide

Category: Network & HTTP 100% Browser-Local

The JSON-RPC Tester is an interactive workbench designed for testing JSON-RPC 2.0 protocol endpoints. It facilitates constructing compliant request envelopes with jsonrpc: "2.0", method, params, and id fields.

Users can configure custom endpoints and headers, dispatch calls, and inspect structured responses distinguishing between successful result bodies and error structures (code, message, data). It also tracks request history for rapid iteration.

#json-rpc #api #test #rpc #request

Key Features & Capabilities

  • Strict JSON-RPC 2.0 compliance supporting both positional (array) and named (object) params
  • Configurable target RPC endpoint URL, custom headers, and automatic ID counter incrementation
  • Clear visual separation between successful result payloads and standard RPC error envelopes
  • Built-in request history and preset templates for efficient regression testing

How to Use

  1. 1

    Enter the target JSON-RPC server endpoint URL (e.g. an Ethereum node or microservice URL).

  2. 2

    Specify the RPC method string and input valid JSON array or object params.

  3. 3

    Click Send Request to dispatch the call and review the formatted result or error object.

Common Use Cases

  • → Debugging blockchain JSON-RPC endpoints on Ethereum or EVM chains (e.g. eth_blockNumber, eth_call)
  • → Verifying internal microservice communication interfaces adhering to JSON-RPC 2.0 specifications
  • → Testing embedded hardware devices and IoT gateways exposing RPC control protocols

Related Tools

Frequently Asked Questions & Privacy

What defines a Notification in JSON-RPC 2.0?

A Notification is a request object that intentionally omits the "id" member. The server does not reply to notifications with any response.

What are standard JSON-RPC 2.0 error codes?

Standard codes include -32700 (Parse error), -32600 (Invalid Request), -32601 (Method not found), -32602 (Invalid params), and -32603 (Internal error).