{ "openrpc": "1.2.6", "servers": [ { "url": "https://{cloudprovider-region}.json-rpc.cryptoapis.io/nodes/shared/${blockchain}/${network}", "x-example": "https://gcp-europe-west1-c.json-rpc.cryptoapis.io/nodes/shared/${blockchain}/${network}", "description": "JSON-RPC API" } ], "x-headers": [ { "name": "X-API-Key", "description": "API Key Authorization Header", "value": "your-api-key" }, { "name": "Content-Type", "description": "Content Type Header", "value": "application/json" } ], "info": { "title": "CryptoAPIs", "version": "2.0.0", "versionId": "6707d1a92c703bd75268a9d9", "id": "6707d1aa2feff07686e31030", "description": "Crypto APIs is a complex and innovative infrastructure layer that radically simplifies the development of any Blockchain and Crypto related applications. Organized around REST, Crypto APIs can assist both novice Bitcoin/Ethereum enthusiasts and crypto experts with the development of their blockchain applications. Crypto APIs provides unified endpoints and data, raw data, automatic tokens and coins forwardings, callback functionalities, and much more.", "termsOfService": "https://cryptoapis.io/terms-conditions/", "contact": { "name": "Crypto APIs Team", "url": "https://cryptoapis.io", "email": "developers@cryptoapis.io" }, "license": { "name": "MIT", "url": "http://www.opensource.org/licenses/mit-license.php" } }, "tags": [ { "name": "Overview", "description": "## Introduction\r\n\r\nNode as a Service (NaaS) by Crypto APIs is a service that provides access and maintenance to shared and dedicated nodes for multiple blockchains and networks.\r\n\r\nAs a node service provider, we host and take care of your nodes while you focus on the business project you\u2019re working on without the hassle of operating a node infrastructure.\r\n\r\nCrypto APIs offers two types of node services - shared, dedicated.\r\n\r\nWe operate with a pool of nodes distributed across multiple locations, which allows for quick response time and high availability. For more information view our [Node as a Service](https://cryptoapis.io/products/node-as-a-service) page.\r\n\r\n## What we support\r\n\r\n##### Nodes public networks\r\n\r\n{note} It is important that the public URL is always: https://gcp-europe-west1-c.json-rpc.cryptoapis.io/nodes/shared/*blockchain/*network {/note}\r\n\r\n\r\n| Blockchain | Network | Shared Node | Dedicated Node | Ready to use |Offical Documentation | Webhooks | \r\n| -------- | -------- | -------- |\r\n| Bitcoin | Mainnet & Testnet | Yes | [Contact Us](https://cryptoapis.io/contacts) | Yes | https://developer.bitcoin.org/reference/rpc/|[Yes](https://developers.cryptoapis.io/technical-documentation/api/blockchain-events/create-subscriptions-for/new-confirmed-coins-transactions)|\r\n| Litecoin | Mainnet & Testnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://litecoin.info/index.php/Litecoin_API| [Yes](https://developers.cryptoapis.io/technical-documentation/api/blockchain-events/create-subscriptions-for/new-confirmed-coins-transactions)\r\n| Dogecoin | Mainnet & Testnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://docs.dogechain.dog/docs/get-started/json-rpc-commands| [Yes](https://developers.cryptoapis.io/technical-documentation/api/blockchain-events/create-subscriptions-for/new-confirmed-coins-transactions)\r\n| Bitcoin cash | Mainnet & Testnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://docs.bitcoincashnode.org/doc/json-rpc/ | [Yes](https://developers.cryptoapis.io/technical-documentation/api/blockchain-events/create-subscriptions-for/new-confirmed-coins-transactions)\r\n| Ethereum | Mainnet & Testnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://ethereum-json-rpc.com/| [Yes](https://developers.cryptoapis.io/technical-documentation/api/blockchain-events/create-subscriptions-for/new-confirmed-coins-transactions)\r\n| Ethereum-Classic | Mainnet & Mordor | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes|https://ethereum-json-rpc.com/ | [Yes](https://developers.cryptoapis.io/technical-documentation/api/blockchain-events/create-subscriptions-for/new-confirmed-coins-transactions)\r\n| Binance-smart-chain | Mainnet & Testnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes|https://ethereum-json-rpc.com/ | [Yes](https://developers.cryptoapis.io/technical-documentation/api/blockchain-events/create-subscriptions-for/new-confirmed-coins-transactions)\r\n| Zcash | Mainnet & Testnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes|https://zcash.github.io/rpc/| [Yes](https://developers.cryptoapis.io/technical-documentation/api/blockchain-events/create-subscriptions-for/new-confirmed-coins-transactions)\r\n| XRP | Mainnet & Testnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://xrpl.org/account-methods.html#account-methods | [Yes](https://developers.cryptoapis.io/technical-documentation/api/blockchain-events/create-subscriptions-for/new-confirmed-coins-transactions)\r\n| Dash | Mainnet & Testnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://docs.dash.org/projects/core/en/stable/docs/api/remote-procedure-calls-dash.html | [Yes](https://developers.cryptoapis.io/technical-documentation/api/blockchain-events/create-subscriptions-for/new-confirmed-coins-transactions)\r\n| Polygon | Mainnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://github.com/0xPolygon/polygon-edge/blob/develop/docs/docs/api/json-rpc-eth.md | [Yes](https://developers.cryptoapis.io/technical-documentation/api/blockchain-events/create-subscriptions-for/new-confirmed-coins-transactions)\r\n| Arbitrum | Mainnet & Sepolia | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://docs.arbitrum.io/sdk | [Yes](https://developers.cryptoapis.io/technical-documentation/api/blockchain-events/create-subscriptions-for/new-confirmed-coins-transactions)\r\n| Optimism | Mainnet & Sepolia | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://community.optimism.io/docs/developers/build/differences/#json-rpc-differences | [Yes](https://developers.cryptoapis.io/technical-documentation/api/blockchain-events/create-subscriptions-for/new-confirmed-coins-transactions)\r\n| Solana | Mainnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://docs.solana.com/api/http | Coming soon\r\n| Fantom | Mainnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://docs.fantom.foundation/technology/overview | Coming soon\r\n| Tron | Mainnet & Nile | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://developers.tron.network/reference/eth_blocknumber | [Yes](https://developers.cryptoapis.io/technical-documentation/api/blockchain-events/create-subscriptions-for/new-confirmed-coins-transactions)\r\n| Near | Mainnet | Yes | [Contact Us](https://cryptoapis.io/contacts)|Yes| https://docs.near.org/api/rpc/introduction | Coming soon\r\n| Filecoin | Mainnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://docs.filecoin.io/reference/json-rpc | Coming soon\r\n| SUI | Mainnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://docs.sui.io/sui-api-ref | Coming soon\r\n| Avalanche | Mainnet & Fuji | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://ethereum-json-rpc.com/ |[Yes](https://developers.cryptoapis.io/technical-documentation/api/blockchain-events/create-subscriptions-for/new-confirmed-coins-transactions) \r\n| Base | Mainnet & Sepolia | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://ethereum-json-rpc.com/ |[Yes](https://developers.cryptoapis.io/technical-documentation/api/blockchain-events/create-subscriptions-for/new-confirmed-coins-transactions)\r\n| Cronos | Mainnet | Yes | [Contact Us](https://cryptoapis.io/contacts)|Yes| https://ethereum-json-rpc.com/| Coming soon\r\n| Aurora | Mainnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://ethereum-json-rpc.com/| Coming soon\r\n| Gnosis | Mainnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://ethereum-json-rpc.com/| Coming soon\r\n| Harmony | Mainnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://ethereum-json-rpc.com/| Coming soon\r\n| Starknet | Mainnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://github.com/starkware-libs/starknet-specs/blob/master/api/starknet_api_openrpc.json| Coming soon\r\n| Scroll | Mainnet & Testnet | Yes | [Contact Us](https://cryptoapis.io/contacts) | Yes| https://ethereum-json-rpc.com/| Coming soon\r\n| Berachain | Testnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://ethereum-json-rpc.com/| Coming soon\r\n| Blast | Mainnet & Testnet | Yes | [Contact Us](https://cryptoapis.io/contacts) |Yes| https://ethereum-json-rpc.com/| Coming soon" }, { "name": "Authentication NaaS", "description": "## Create API key\r\n \r\n API keys are required for authentication with Crypto APIs products. Without a valid API key, access to the API is denied. \r\n \r\n You can generate and manage API keys from within the Crypto APIs Dashboard. By clicking on \"Create new API key\" you can enter a name and the system will generate a unique key for API authentication. \r\n Multiple keys can be generated. Old API keys that you no longer want to use can be disabled from the same location. \r\n \r\n ## Use API key \r\n\r\n API keys are required for the authentication of the calling program to the API. All Crypto APIs keys use the same base URL `https://rest.cryptoapis.io`. They can be used in test environments such as: \r\n Development, QA, and main Production environments.\r\n \r\n We do not recommend using the same API key for more than one environment. We recommend using a single key for one specific environment - Testing, Production, etc. The API key is sensitive private \r\n information that we strongly advise to keep restricted access to.\r\n \r\n ### Header Authentication (Recommended) \r\n\r\n Pass the API key in the `X-API-Key` request header:\r\n\r\n Content-Type: application/json \r\n X-API-Key: my-api-key\r\n \r\n This is the recommended method for production environments, as it keeps the API key out of URLs, server access logs, browser history, and proxy logs.\r\n\r\n ### Query Parameter Authentication\r\n\r\n Alternatively, you can pass the API key as a query parameter: \r\n \r\n https://rest.cryptoapis.io/v2/...?apiKey=my-api-key \r\n \r\n This method is useful for quick testing or environments where setting custom headers is not practical.\r\n\r\n > \u26a0\ufe0f **Warning:** Do not provide the API key in both the header and the query parameter in the same request. If both are present, the request will be rejected. \r\n \r\n > \u26a0\ufe0f **Warning:** It's important to secure your API key against public access. Query parameters may appear in server logs, browser history, and referrer headers. For production environments, always use\r\n the header method." }, { "name": "Getting Started NaaS", "description": "## Create an account\r\n\r\nTo get started with Crypto APIs Node-as-a-Service, the first thing you need to do is create your account at https://app.cryptoapis.io/login. By creating an account you get access to a personalized Crypto APIs Dashboard, where you can monitor and control your API keys, requests, credits, and more.\r\n\r\nYou can create your Crypto APIs account manually by adding information to the required fields, or simply use the Social Login provided for Google, GitHub and LinkedIn.\r\n\r\n> **Note:** Please use a valid email address you have access to, in order to be able to receive messages from Crypto APIs needed for user authentication, registration completion and API use.\r\n\r\n> **Note:** Users can also invite Team members by adding their email addresses. Email addresses that already exist as users type \"Owner\" cannot be invited as Team members.\r\n\r\n## The Dashboard\r\n\r\nOnce you create an account, you get access to a personalized Crypto APIs [Dashboard](https://app.cryptoapis.io/). Through the dashboard is where you can subscribe to and manage the Node-as-a-Service product.\r\n\r\nFrom the Dashboard you can:\r\n\r\n- Create and manage API keys \u2014 for authentication of your JSON-RPC requests\r\n- Monitor successful and failed requests and credits\r\n- Manage your subscription plan\r\n\r\n## Authenticate requests\r\n\r\nTo make JSON-RPC calls through the Node-as-a-Service gateway, you must create an API key so that your requests are authenticated.\r\n\r\nAn API key is a code unique to the user who generated it. It is used to identify the call to the API and track access and usage. You can generate your API key from within the Crypto APIs [Dashboard](https://app.cryptoapis.io) by clicking on the \"Create new API key\" button. You can generate more than one API key and use a single API key more than once.\r\n\r\n### Header Authentication (Recommended)\r\n\r\nPass the API key in the `X-API-Key` request header:\r\n\r\n```\r\nPOST https://gcp-europe-west1-c.json-rpc.cryptoapis.io/nodes/shared/{protocol}/{network}\r\nContent-Type: application/json\r\nX-API-Key: my-api-key\r\n```\r\n\r\nThis is the recommended method for production environments, as it keeps the API key out of URLs, server access logs, browser history, and proxy logs.\r\n\r\n### Query Parameter Authentication\r\n\r\nAlternatively, you can pass the API key as an `apiKey` query parameter:\r\n\r\n```\r\nPOST https://gcp-europe-west1-c.json-rpc.cryptoapis.io/nodes/shared/{protocol}/{network}?apiKey=my-api-key\r\n```\r\n\r\nThis method is useful for quick testing or environments where setting custom headers is not practical.\r\n\r\n> \u26a0\ufe0f **Warning:** Do not provide the API key in both the header and the query parameter in the same request. If both are present, the request will be rejected.\r\n\r\n> \u26a0\ufe0f **Warning:** It's important to secure your API key against public access. Query parameters may appear in server logs, browser history, and referrer headers. For production environments, always use the header method." } ], "methods": [], "x-tagGroups": [ { "name": "General Information", "tags": [ "Overview", "Getting Started NaaS", "Authentication NaaS", "Supported Protocols" ] } ] }