Securing exchange API credentials

An exchange API credential is a secret that can authorise actions on an account. Disabling withdrawals materially limits one route of abuse, but a trade-enabled key can still create losses through unwanted orders. Security therefore depends on reducing permissions, exposure and lifetime — not on one control.

Create the least-powerful key

• Create a separate key for CryptoMetric AI instead of reusing one across services.
• Enable only the trading permission the intended market requires.
• Never enable withdrawals or transfers.
• Restrict the key to the service IP address when the exchange supports it.
• Start with an exchange testnet or sandbox where its behaviour is supported and understood.

The user creates and controls the key in their own exchange account. CryptoMetric AI cannot verify every exchange-side permission, so the user must review those settings directly and follow the exchange's current security guidance.

What the platform does

Submitted API keys, secrets and optional passphrases are encrypted with Fernet before database storage. Credential responses return a fixed mask rather than plaintext. The trading worker decrypts the secret in application memory when it needs to construct an exchange session. New credential records default to testnet mode.

Encryption at rest reduces exposure if database contents are obtained without the separate encryption key. It does not make credentials invulnerable: a compromised running application, host, administrator account or user session may still be able to exercise authorised access. No system is breach-proof.

Operate the key as a revocable secret

Keep exchange login and multi-factor authentication independent of the bot. Review exchange order and login history, platform audit events and alerts. Rotate a credential after personnel or infrastructure changes, and revoke it immediately after suspected compromise, unexpected activity or when the bot no longer needs access. Deleting a credential from the platform is not a substitute for revoking it at the exchange.

If something looks wrong

1. Use the exchange directly to cancel orders and manage open positions.
2. Revoke the API key at the exchange; do not wait for an application-side deletion.
3. Change the exchange password and review multi-factor authentication and active sessions.
4. Preserve timestamps, order records and relevant audit evidence before it expires.
5. Create a new least-privilege key only after the cause is understood.

Credential safeguards reduce likelihood and impact. They cannot guarantee uninterrupted service, prevent every misuse or make automated trading safe from financial loss.