Manage API Calls
Currently, Cobo MPC Lite supports two types of REST APIs:
- Querying: This API endpoint is used to retrieve information such as addresses, balances and transaction history.
- Withdrawal and Querying: In addition to the query functionality, this API endpoint allows the initiation of withdrawal requests.
The API key serves as your authentication credential when communicating with Cobo servers through APIs. It must be stored securely. Cobo will only collect your public key for signature verification and, under no circumstances, will Cobo request your private key. Kindly ensure not to disclose your private key to anyone to prevent any potential loss of assets.
Cobo uses ECDSA signatures for verification. Please generate a public-private key pair locally and key in your API key under the 'API Key' field as shown in the above image. For guidance on generating key pairs and signature authentication, kindly refer to this guide. If you have any questions, please contact us at firstname.lastname@example.org.
You can edit the description or add an IP for your API key but cannot modify the public key. If you lose the private key, please delete the corresponding API key promptly and generate a new public-private key pair as a replacement.
There is no limit to the number of API keys each user can create. Each key can be linked to multiple IP addresses, separated by commas, such as 192.168.1.1,192.168.1.2. Note that the admins will need to approve the request to add API keys and/or update the IP whitelist in Cobo Auth.
Manage API Callbacks
When Cobo receives a successful deposit or withdrawal transaction (i.e., the block confirmation threshold has been met), it will send an HTTP(s) message to the URL specified by the customer. The message is sent using the POST request method. Simply click the 'Add' button on the right to set up this callback URL.