Getting Started NaaS

Create an account

To 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.

You 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.

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.

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.

The Dashboard

Once you create an account, you get access to a personalized Crypto APIs Dashboard. Through the dashboard is where you can subscribe to and manage the Node-as-a-Service product.

From the Dashboard you can:

• Create and manage API keys — for authentication of your JSON-RPC requests
• Monitor successful and failed requests and credits
• Manage your subscription plan

Authenticate requests

To make JSON-RPC calls through the Node-as-a-Service gateway, you must create an API key so that your requests are authenticated.

An 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 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.

Header Authentication (Recommended)

Pass the API key in the X-API-Key request header:

POST https://gcp-europe-west1-c.json-rpc.cryptoapis.io/nodes/shared/{protocol}/{network}
Content-Type: application/json
X-API-Key: my-api-key

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.

Query Parameter Authentication

Alternatively, you can pass the API key as an apiKey query parameter:

POST https://gcp-europe-west1-c.json-rpc.cryptoapis.io/nodes/shared/{protocol}/{network}?apiKey=my-api-key

This method is useful for quick testing or environments where setting custom headers is not practical.

⚠️ 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.

⚠️ 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.