API Frequently Asked Questions

• I'm using a third-party service/wrapper, and it is not working. Can you help?

Unfortunately, we do not support third-party services or tools. Please reach out to the service and/or developers for further assistance.

In addition, it is a security risk to enter your Coincall API Key(s) and/or Secret(s) into any third-party platform. Please use these services at your own discretion.

Keep in mind that we also avoid providing general programming assistance.

• Despite making no changes, I'm suddenly receiving errors. What happened?

Unfortunately, we are unable to provide support for issues with your personal implementation. If you are using a third-party wrapper/tool, please contact their support/development team for assistance.

• I need to access my API Secret, but it displays "***". How do I retrieve this?*

For security reasons, by design, API Secrets are only visible at the time the API Key is created. Any time after that point, it will be masked. If you have lost it, or you did not record it, you will need to create a new API Key and utilize the new key with a new API Secret.

• Can I request new API functionalities?

If you do not see the functionality you are requesting in our documentation, you should assume that we do not provide it. If you would like to make a feature suggestion, you may open a support ticket, and it will be reviewed.

• I believe there is an issue with the API. How should I report it?

If you feel there is an issue with the system and not with your implementation, please provide evidence to support your claim by opening a support ticket, and we will investigate it. Please be informed that we do not accept vague messages as legitimate complaints.

• How can I ensure that I'm using the most up-to-date data?

1. When using the REST API or (although less likely) websocket, there is a possibility (though unlikely) of receiving or being pushed outdated data.
2. To achieve the highest level of data flexibility, we recommend the following steps to our clients:
   • Firstly, prioritize reliance on the websocket. It not only ensures that you receive the latest data at the fastest speed, but also guarantees the receipt of complete data sets. This is crucial for trading purposes.
   • Secondly, use the REST API to query and fill in any differences within the data, especially differences that may occur when the websocket connection is disrupted.
3. Best practice involves storing all of this data locally in your own database or cache.
4. This approach not only frees you from rate limitations on other requests but also ensures that you can operate at a redundant level within the exchange in case of data transmission delays. This maintains the reliability and accuracy of trading operations.

Check with API Doc：https://docs.coincall.com/#overview