From 6c5b4cd402539745222694a2ec2f0068834b0cd8 Mon Sep 17 00:00:00 2001 From: Pablo Adell Date: Tue, 26 Nov 2024 23:42:52 +0100 Subject: [PATCH] Fix ID types to match JSON-RPC 2.0 spec (#569) * Update index.mdx updating description of id key according to [`JSON RPC 2.0` standard](https://www.jsonrpc.org/specification#request_object) * Update index.mdx * Update docs/rpc/http/index.mdx * Update index.mdx Updating description based on specification --------- Co-authored-by: Mike MacCana --- docs/rpc/http/index.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/rpc/http/index.mdx b/docs/rpc/http/index.mdx index ddcaa9649..0392e5605 100644 --- a/docs/rpc/http/index.mdx +++ b/docs/rpc/http/index.mdx @@ -29,7 +29,9 @@ To make a JSON-RPC request, send an HTTP POST request with a fields: - `jsonrpc: ` - set to `"2.0"` -- `id: ` - a unique client-generated identifying integer +- `id: ` - a unique identifier for the request, + generated by the client. Typically a string or number, though null is + technically allowed but not advised - `method: ` - a string containing the method to be invoked - `params: ` - a JSON array of ordered parameter values