Exchange verification didn’t pass
When you save an account, Trade verifies your API key with the exchange and doesn’t save if the check fails. The message names the reason. Fix it and save again.
What it means
When you saved the account, Trade verified the API key you entered with the exchange. The check didn’t pass, so the account wasn’t saved. The reason follows the colon in the message.
Reasons and fixes
| Reason in the message | What to do |
|---|---|
| API key is wrong | Copy the API key from the same creation again and check for missing or extra characters |
| The API permissions are insufficient | On the exchange, turn on the permissions listed under Enable in the API key section of the add-account window |
| The IP allowlist doesn’t include the server | In the add-account window, choose Copy all egress IPs and add them to the API key’s IP allowlist |
| A problem with the API key, IP allowlist or permissions | Check all three |
| The server clock doesn’t match the exchange | Sync the server clock |
| The exchange has temporarily locked or restricted API requests for this account | Save again in a little while. Every retry is rejected during the restriction |
| Can’t reach the exchange | Try again in a moment, and check the server network if it keeps failing |
| The account mode doesn’t meet the requirements | Switch to a supported account mode on the exchange |
| The account isn’t activated yet | Complete account activation on the exchange (for example, Aster requires the linked main wallet to have made a deposit), then save again |
| The account settings don’t meet the requirements | Change the account settings on the exchange to a supported mode, then save again |
If verification still fails, expand the exchange response in the message for the specific reason. For the setup steps, see Connect an exchange.