From 774966641c068c340ef1069c7d8d0adb325c2d4d Mon Sep 17 00:00:00 2001 From: "juraj.bacovcin" Date: Fri, 19 Apr 2024 10:26:16 +0200 Subject: [PATCH] fixing rpcs as per request from Nader and Nestor --- categories/blockchain_node_rpc/openapi.yml | 2 +- ...n_node_{chain}_{xApiKey}_{rpcPath}_get.yml | 13 +---- ..._node_{chain}_{xApiKey}_{rpcPath}_post.yml | 56 +------------------ ...n_node_{chain}_{xApiKey}_{rpcPath}_put.yml | 16 +----- 4 files changed, 7 insertions(+), 80 deletions(-) diff --git a/categories/blockchain_node_rpc/openapi.yml b/categories/blockchain_node_rpc/openapi.yml index e328f98..53878d5 100644 --- a/categories/blockchain_node_rpc/openapi.yml +++ b/categories/blockchain_node_rpc/openapi.yml @@ -11,7 +11,7 @@ tags: the supported blockchains is provided in the API description further in this section.

" - name: Node RPC + name: Connecting to v3 REST API servers: - url: https://api.tatum.io paths: diff --git a/categories/blockchain_node_rpc/paths/v3_blockchain_node_{chain}_{xApiKey}_{rpcPath}_get.yml b/categories/blockchain_node_rpc/paths/v3_blockchain_node_{chain}_{xApiKey}_{rpcPath}_get.yml index f7dc207..72ae5fb 100644 --- a/categories/blockchain_node_rpc/paths/v3_blockchain_node_{chain}_{xApiKey}_{rpcPath}_get.yml +++ b/categories/blockchain_node_rpc/paths/v3_blockchain_node_{chain}_{xApiKey}_{rpcPath}_get.yml @@ -1,16 +1,7 @@ description: "

2 credits per RPC method in an API call

\n

Connect directly\ \ to the blockchain node provided by Tatum.

\n

The GET method\ - \ is used. The API endpoint URL acts as an HTTP-based RPC driver.

\n

This API\ - \ is supported for the following blockchains:

\n\n" + \ is used. The API endpoint URL acts as an HTTP-based RPC driver.

\n" operationId: NodeJsonRpcGetDriver parameters: - description: @@ -76,4 +67,4 @@ responses: x-codeSamples: [] summary: Connect to the blockchain node through an RPC driver tags: - - Node RPC + - Connecting to v3 REST API diff --git a/categories/blockchain_node_rpc/paths/v3_blockchain_node_{chain}_{xApiKey}_{rpcPath}_post.yml b/categories/blockchain_node_rpc/paths/v3_blockchain_node_{chain}_{xApiKey}_{rpcPath}_post.yml index e92f59f..2cb683f 100644 --- a/categories/blockchain_node_rpc/paths/v3_blockchain_node_{chain}_{xApiKey}_{rpcPath}_post.yml +++ b/categories/blockchain_node_rpc/paths/v3_blockchain_node_{chain}_{xApiKey}_{rpcPath}_post.yml @@ -5,59 +5,7 @@ description: \ target=\"_blank\">Trace API methods
\n* 5 credits per eth_call method\ \ (for EVM-based blockchains)
\n* 2 credits per any other RPC method

\n\

Connect directly to the blockchain node provided by Tatum.

\n

The POST\ - \ method is used. The API endpoint URL acts as an HTTP-based RPC driver.

\n

In\ - \ the request body, provide valid Web3 RPC method content, for example:

\n
\n\
-  {\n  \"jsonrpc\": \"2.0\",\n  \"id\": 1,\n  \"method\": \"method_name\",\n  \"params\"\
-  : []\n}\n
\n

For the blockchains using the JSON-RPC 2.0 specification, you\ - \ can submit multiple RPC methods in one API call:

\n
\n[\n  {\n    \"jsonrpc\"\
-  : \"2.0\",\n    \"id\": 1,\n    \"method\": \"method_1_name\",\n    \"params\":\
-  \ []\n  },\n  {\n    \"jsonrpc\": \"2.0\",\n    \"id\": 2,\n    \"method\": \"method_2_name\"\
-  ,\n    \"params\": []\n  },\n  ...\n]\n
\n

This API is supported for the\ - \ following blockchains:

\n\n" + \ method is used. The API endpoint URL acts as an HTTP-based RPC driver.

\n" operationId: NodeJsonPostRpcDriver parameters: - description: @@ -137,4 +85,4 @@ responses: x-codeSamples: [] summary: Connect to the blockchain node through an RPC driver tags: - - Node RPC + - Connecting to v3 REST API diff --git a/categories/blockchain_node_rpc/paths/v3_blockchain_node_{chain}_{xApiKey}_{rpcPath}_put.yml b/categories/blockchain_node_rpc/paths/v3_blockchain_node_{chain}_{xApiKey}_{rpcPath}_put.yml index 75d7e9c..e67ba14 100644 --- a/categories/blockchain_node_rpc/paths/v3_blockchain_node_{chain}_{xApiKey}_{rpcPath}_put.yml +++ b/categories/blockchain_node_rpc/paths/v3_blockchain_node_{chain}_{xApiKey}_{rpcPath}_put.yml @@ -1,19 +1,7 @@ description: "

2 credits per RPC method in an API call

\n

Connect directly\ \ to the blockchain node provided by Tatum.

\n

The PUT method\ - \ is used. The API endpoint URL acts as an HTTP-based RPC driver.

\n

In the\ - \ request body, provide valid Web3 RPC method content, for example:

\n
\n\
-  {\n  \"jsonrpc\": \"2.0\",\n  \"id\": 1,\n  \"method\": \"method_name\",\n  \"params\"\
-  : []\n}\n
\n

For the blockchains using the JSON-RPC 2.0 specification, you\ - \ can submit multiple RPC methods in one API call:

\n
\n[\n  {\n    \"jsonrpc\"\
-  : \"2.0\",\n    \"id\": 1,\n    \"method\": \"method_1_name\",\n    \"params\":\
-  \ []\n  },\n  {\n    \"jsonrpc\": \"2.0\",\n    \"id\": 2,\n    \"method\": \"method_2_name\"\
-  ,\n    \"params\": []\n  },\n  ...\n]\n
\n

This API is supported for the\ - \ following blockchains:

\n\n" + \ is used. The API endpoint URL acts as an HTTP-based RPC driver.

\n" operationId: NodeJsonRpcPutDriver parameters: - description: @@ -94,4 +82,4 @@ responses: x-codeSamples: [] summary: Connect to the blockchain node through an RPC driver tags: - - Node RPC + - Connecting to v3 REST API