JSON-RPC Envelope and Batch Workbench
Inspect JSON-RPC 2.0 envelopes or correlate supplied batch replies with exact request IDs.
Loading tool…
How to use JSON-RPC Envelope and Batch Workbench
Inspect JSON-RPC 2.0 envelopes or correlate supplied batch replies with exact request IDs. Distinguish notifications from calls, result from error, and numeric IDs from string IDs. Invalid individual messages receive diagnostics; no method is executed.
- Provide messages or request batch, response batch (blank for no response).
- Choose the supported mode and run the tool. Review its assumptions and any reported errors.
- Copy the result or download a separate output; reset to clear the current form.
Good to know
- 100 KB per JSON document, 100 messages, 40 levels and 100,000 JSON values. Prototype-related object keys are refused.
- The supported profile uses IDs that are bounded strings, null or safe whole numbers; fractional/unsafe numeric IDs are refused to preserve correlation identity. Duplicate IDs are reported as ambiguous.
- Missing responses and unexpected IDs do not prove a transport failure. Extension semantics, batch error recovery and method-specific parameter/result schemas are not inferred.
- Inputs are processed on this device and are not automatically saved or uploaded.
Common questions
Are notifications expected to have replies?
No. A request without an id is a notification. Correlation reports it separately and does not expect a response for it.
Does this change my original input?
No. The tool returns a separate result. Review that output before using it in another application.
Keep going with related tools
All developer →JSON Validator
Check JSON syntax locally and see its root type, value count, and nesting depth.
DeveloperHTTP Message Framing Inspector
Inspect one supplied HTTP1 message and decode strictly bounded chunked content offline.
DeveloperServer-Sent Events Stream Workbench
Parse event-stream source or create an SSE artifact from explicit event data without opening a connection.