Authentication NaaS

Create API key

API keys are required for authentication with Crypto APIs products. Without a valid API key, access to the API is denied.

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.
Multiple keys can be generated. Old API keys that you no longer want to use can be disabled from the same location.

Use API key

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:
Development, QA, and main Production environments.

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
information that we strongly advise to keep restricted access to.

Header Authentication (Recommended)

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

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 a query parameter:

https://rest.cryptoapis.io/v2/...?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.