JSON-RPC Request Tester Tool

Test your JSON-RPC APIs by sending requests and analyzing responses in real-time without writing any code.

On this page

Ready to test your API?

Try the Request Tester tool now to send JSON-RPC requests.

Go to Request Tester

Overview

The JSON-RPC Request Tester tool allows you to test your JSON-RPC APIs directly from your browser. You can send requests to any JSON-RPC endpoint, view responses, and store your testing history for future reference. The tool helps you debug and validate your API implementations without writing any additional code.

Pro Tip: Save your frequently used requests for quick access during development and testing cycles.

Features

Endpoint Testing

Send requests to any JSON-RPC endpoint

Request History

Save and manage your testing history

Environment Configs

Configure multiple environments (dev, test, prod)

Performance Metrics

View response times and other performance data

Custom Headers

Add authentication and other custom headers

Response Analysis

Detailed response inspection with syntax highlighting

Usage Guide

Sending a Basic Request

To send a JSON-RPC request:

  1. Enter the endpoint URL in the URL field (e.g., https://api.example.com/jsonrpc)
  2. Select the HTTP method (usually POST for JSON-RPC)
  3. Enter your JSON-RPC request in the request body area
  4. Add any required headers (Content-Type: application/json is added by default)
  5. Click the "Send Request" button
  6. View the response and performance metrics

Example Request

// Request Body
{
  "jsonrpc": "2.0",
  "method": "getUser",
  "params": {"id": 123},
  "id": 1
}

// Headers
Content-Type: application/json
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...

Analyzing Responses

The response area displays:

  • HTTP status code
  • Response time
  • Response headers
  • Formatted JSON response body with syntax highlighting
  • Error information (if applicable)

Example Response

// Response Body
{
  "jsonrpc": "2.0",
  "result": {
    "id": 123,
    "name": "John Doe",
    "email": "[email protected]"
  },
  "id": 1
}

// Status: 200 OK
// Time: 187ms

Request History

The Request Tester tool automatically saves your request history for easy reference and reuse.

Working with Request History

Saving Requests

Click the "Save" button after sending a request to save it to your history with a custom name. Saved requests are stored in your browser's local storage.

Loading Previous Requests

Open the history panel to view your saved requests. Click on any request to load it into the editor. You can also search and filter your history.

Organizing Requests

Group related requests into collections for better organization. You can create, edit, and delete collections from the history panel.

Exporting and Importing

Export your request history to a JSON file for backup or sharing. You can also import requests from a file.

Environment Setup

Configure different environments to easily switch between testing contexts.

Environment Configuration

// Development Environment
{
  "name": "Development",
  "baseUrl": "https://dev-api.example.com/jsonrpc",
  "headers": {
    "Authorization": "Bearer dev-token"
  }
}

// Production Environment
{
  "name": "Production",
  "baseUrl": "https://api.example.com/jsonrpc",
  "headers": {
    "Authorization": "Bearer prod-token"
  }
}

Environment variables can be referenced in your requests using {variable_name} syntax.

Troubleshooting

Common issues and their solutions when working with the Request Tester.

Common Issues

CORS Errors

If you encounter Cross-Origin Resource Sharing (CORS) errors, the API server needs to allow requests from the tester's domain.

Solution: Configure your API server to include appropriate CORS headers, or use a CORS proxy.

Authentication Issues

If your API requires authentication, ensure you're including the correct authentication headers.

Solution: Check your bearer token or other credentials. Use the environment configuration for different auth contexts.

Connection Timeout

If your request times out, the server might be unresponsive or unreachable.

Solution: Verify the endpoint URL and check if the server is running. Consider increasing the timeout setting.

Invalid JSON

If your request contains invalid JSON, the server will reject it.

Solution: Use the JSON validator tool to check your request body before sending.

Best Practices

Recommended Practices

  • Organize related requests into collections for easier testing
  • Use environment configurations for different deployment scenarios
  • Validate your JSON-RPC requests before sending them
  • Regularly export your request collections for backup
  • Monitor performance metrics to identify slow endpoints
  • Use batch requests when testing multiple related operations