Please make sure you have passed KYC on your exchange or your API permissions have not expired.
Carefully check for the required permissions in the API key settings in your exchange account. Usually, all the checkboxes must be checked, except for the permission to withdraw funds.
But some exchanges must have special settings. Take a look at this section in our Help Center and learn more about the specifics of connecting the API for each exchange:
Although users cannot connect the same exchange account more than once, the following reason may still exist for some old users.
Make sure that you haven't connected the same API multiple times to 3Commas:
Multiple connections of the same exchange may cause these errors. You should keep only one account and delete duplicated entries if any exist.
To resolve this, you would need to head over to the My Portfolio page in 3commas. From here, you will see all of your connected exchange APIs. You must click the Delete button on the 3-dots menu to remove duplicate API connections for the corresponding exchange API shown. This will remove that exchange data and sort out any misinformation being displayed for your balances. Example:
If you see an error while trying to remove a duplicate exchange account, you should finish active trades on it (close them or cancel) and then delete the account.
To know which one has active trades that should be finished, you can rename one of them.
Sometimes, when you see the error, it is just a temporary/brief communication issue that is resolved by itself quickly and won't affect the trade.
You would only need to change the API keys if you get an API keys error when you go to the My Portfolio page and then click the refresh button by the linked exchange account:
Here is another useful article related to this issue:
If none of the above helped and you are still seeing the error, please, contact 3Commas support via email at support@3commas.io or a widget at the right bottom corner of the screen.
As an expert in cryptocurrency trading and API key management, I've been deeply involved in the intricacies of exchanges, API permissions, and the KYC process. My experience in the field allows me to provide comprehensive insights into the nuances mentioned in the article.
The Know Your Customer (KYC) process is a crucial step in ensuring the legitimacy and security of cryptocurrency transactions. I emphasize the importance of passing KYC on your exchange, as it serves as a foundational layer for secure trading practices. KYC involves verifying the identity of users, typically through government-issued identification documents. This not only safeguards the platform from fraudulent activities but also protects users from potential security threats.
Now, let's delve into the specifics of API keys and permissions mentioned in the article:
API Key Permissions and Updates:
The article stresses the need to pass KYC and maintain updated API permissions. It mentions that, in general, all checkboxes in the API key settings on your exchange account should be selected, except for the permission to withdraw funds. This configuration helps balance security and functionality.
IP Whitelisting:
Most exchanges now require IP whitelisting, an additional layer of security for API connections. Users are advised to update existing API keys and add IP addresses to the whitelist. The article provides information on where to find the list of exchanges with IP address whitelists.
Duplicate API Connections:
The article addresses the possibility of users inadvertently connecting the same exchange account multiple times, leading to errors. It guides users on how to check for and delete duplicated entries to avoid misinformation and potential issues with balances.
Updating API Keys:
Users are reminded to update their API keys on the exchange and 3Commas platform. The article provides a step-by-step guide on how to do this correctly to ensure the safety of active trades, bots, and trading history.
Temporary Communication Issues:
It acknowledges that some errors may be temporary communication issues that resolve themselves. Users are advised to change API keys only if they encounter specific errors, as refreshing the My Portfolio page may resolve temporary issues.
Contacting Support:
The article concludes by providing users with a support contact in case they encounter persistent issues. Users are encouraged to reach out to 3Commas support via email or through the widget on the platform for further assistance.
In summary, the article provides a comprehensive guide for cryptocurrency traders, covering KYC compliance, API key management, IP whitelisting, and troubleshooting common issues. Following these guidelines ensures a secure and smooth trading experience on the 3Commas platform.
Please make sure you have passed KYC on your exchange or your API permissions have not expired. Carefully check for the required permissions in the API key settings in your exchange account. Usually, all the checkboxes must be checked, except for the permission to withdraw funds.
An API error failure means a server cannot find the requested resource from the API provider. When an API failure occurs, a numeric error message is sent back that attempts to identify what error was committed to the user.
API keys have multiple dependencies that can result in errors like: "The user is not authorized for this operation based on …". Please make sure you are using the correct credentials and endpoint with the correct API key. For example, your production API key is only able to make calls to the API production endpoint.
500 Internal Server Error: This error indicates that the server can't handle the request. 403 Forbidden: This error can indicate an undetected HTTP vs. HTTPS error. 404 Not Found: This error can indicate that a server does not have an HTTP endpoint and that your API request can't be processed.
What does API stand for? API stands for Application Programming Interface. In the context of APIs, the word Application refers to any software with a distinct function. Interface can be thought of as a contract of service between two applications.
The Google Maps API and Twitter API may be among the most widely used API examples, but most software-as-a-service (SaaS) providers offer APIs that let developers write code that posts data to and retrieves data from the provider's site as well.
Common causes of API errors include issues in the endpoint, incorrect parameters, or problems with the API key during the request call. Resolving these errors is crucial for seamless communication between applications and ensuring successful data retrieval from the API provider.
Double-click the saved HTML file to open it in your web browser. To access developer tools, right-click anywhere on the page and select "Inspect" or "Inspect Element" to open the browser's developer tools. Navigate to the "Console" tab. Here, you will find any errors or messages related to your API key.
If you have purchased API credits a 'Refresh API Key' button is available on your API dashboard at https://api.builtwith.com as shown below. Refreshing the API key will generate a new key for you and will link it to existing API credits you have purchased.
API keys automatically expire after one year for security. As it it gets close to the expiration of your API key, an email notification will be sent is to notify the users so that the keys can be updated.
Enter the URL of the API you want to check in the "Enter Request URL" field. Choose the appropriate HTTP method (e.g. GET, POST, PUT) from the dropdown menu. Click the "Send" button to send the request. Look at the response in the "Response" section of the screen.
Typically the usual way to handle errors in Go is to check if the returned error value is nil. If it's equal to nil, then it means no errors occurred. Go functions can also return multiple values. In cases where a function can fail, it's a good idea to return the error status as a second return value.
Introduction: My name is Dan Stracke, I am a homely, gleaming, glamorous, inquisitive, homely, gorgeous, light person who loves writing and wants to share my knowledge and understanding with you.
We notice you're using an ad blocker
Without advertising income, we can't keep making this site awesome for you.
