Crypto APIs 2.0 Technical Documentation has included vast and detailed information regarding the use of its API services. Additionally, we have prepared various SDKs to help you get quickly started.
You can pick one of our current SDK’s here.
Create an account
To get started with Crypto APIs 2.0 services the first thing you need to do is create your account at https://my.cryptoapis.io/login. By creating an account you get access to a personalized Crypto APIs 2.0 Dashboard, where you can monitor and control your API keys, requests, credits, tokens, exchange accounts, and more.
You can create your Crypto APIs 2.0 account manually by adding information to the required fields, or simply use the Social Login provided for Google, GitHub and LinkedIn.
Once you create an account, you get access to a personalized Crypto APIs 2.0 Dashboard. Through the dashboard is where you can choose and subscribe to a Crypto APIs 2.0 blockchain product - Blockchain Data, Blockchain Events, Blockchain Tools, Blockchain Automations, or Crypto Market Data APIs.
From the Dashboard you can:
- create and manage API keys - for authorization of the API;
- create and manage callback URLs - set URLs for response;
- monitor successful and failed requests, credits, callbacks;
- manage webhooks and tokens;
- create and manage exchange accounts, etc.
The Crypto APIs 2.0 Technical and Best use Documentation is public and available to everyone. Still, support levels for a Crypto APIs 2.0 product vary depending on your subscription.
To use and make calls to any Crypto APIs 2.0 product, you must create an API key, in order for your requests to be authenticated.
An API key is a code unique to the user who generated it. It is used to identify the call to the specific API and track the access to it and its usage. You can generate your API key from within the Crypto APIs 2.0 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.
For more information on Authenticating requests, please see “Authentication” section.