How to create a read-only Crypto.com Exchange API key

Open Crypto.com Exchange API Management ↗

We checked these steps against Crypto.com Exchange's own documentation on 25 September 2026. Crypto.com Exchange can rename a button at any time. If a label differs, look for the same permission.

Before you start

• This connects Crypto.com Exchange, not the Crypto.com App.
• Turn on 2-Factor Authentication in your Exchange account, because Crypto.com asks for it before you can create a key.
• Switch to your Master Account first, because a key reads only the account it is created on.

Permissions

Turn on only:

• Can Read

Keep these off:

• Enable Trading
• Enable Withdrawal
• Connection to Third-Party Applications

Steps

Sovereign connects to Crypto.com Exchange from one fixed IP address. The connection form in Sovereign shows it next to these steps, with a copy button.

1. Click “Open Crypto.com Exchange API Management” above and log in to your Exchange account.
2. Click “Create a new API key”.
3. Check that “Account:” says “Master Account”, then type Sovereign in “Label”.
4. Enter your 2FA code, then click “Create API”.
5. Click “Copy Secret Key” and paste it into API SECRET in Sovereign straight away. Crypto.com shows the secret only once.
6. Back on the API Management page, click “Edit” on the Sovereign key.
7. With “API Key Usage:” on “API Transaction”, paste Sovereign's IP address into “IP Whitelist (Up to 100):”, then press Enter.
8. Click the copy icon next to “API Key:” and paste it into API KEY in Sovereign. Do it now: this window closes once you save.
9. Click “Continue”, then enter your 2FA code to save the change.
10. Once the key is in API KEY and the secret is in API SECRET in Sovereign, press “Connect & Sync”.

Where each value goes in Sovereign:

• Secret Key (from “Copy Secret Key”, shown only once) → API SECRET
• API Key (the “API Key:” field in the key's “Edit” window) → API KEY

Does a Crypto.com Exchange API key expire?

• With an IP restriction: No published expiry rule.
• Without an IP restriction: No published expiry rule.

Crypto.com Exchange publishes no clear expiry rule. If the key stops working, Sovereign marks the connection as expired and asks for a new key.

The IP step is Sovereign's recommendation, not a Crypto.com requirement: Crypto.com only requires an IP whitelist on keys that trade or withdraw, and a read-only key works without one. We still ask for it, because a key locked to our address is worthless anywhere else. A key reads only the account it was created on, so a Master Account key does not include sub-account funds. To track a sub-account, switch to it, create a separate key there and add it as a second connection.

If something goes wrong

• If you don't land on the API page: click your profile icon (top right), then “Manage Account”, then “API Management”.
• If the change doesn't save after you enter your 2FA code: click “Update API Key”.
• If you closed the edit window before copying the API key: click “Edit” on the key again, copy “API Key:”, then click “Cancel”.
• If you lost the secret: delete the key and create a new one, because Crypto.com never shows the secret again.

Sources

• help.crypto.com/en/articles/3511424-api
• static2.crypto.com/exchange/locale/en-US.json
• exchange-developer.crypto.com/exchange/v1/llms-full.txt
• help.crypto.com/en/articles/5580404-sub-accounts