To trade for you, a bot needs an API key from your exchange. The key is like a badge: it defines exactly what the bot is allowed to do. Configured correctly, it lets the bot trade and nothing else. Configured badly, it can hand over your entire balance.
1. Withdrawals always off
This is the rule that matters most. With withdrawals disabled, nobody holding the key can send your coins out of the exchange, not even the platform that received it. Any service asking for a key with withdrawal permission should be refused, no matter how good the promised return looks.
2. Locked to a trusted IP
Binance lets you restrict a key to specific IP addresses. When the key only works from the bot server, a leaked copy is useless on any other computer. Resolutes gives you its server address during setup, and the engine refuses to run with a key that is not locked.
3. Only the permissions needed
For spot trading, the bot needs to read the account and place spot orders. Margin, futures and transfers between accounts stay off unless the strategy truly requires them. Fewer permissions mean less damage if anything goes wrong.
Step by step on Binance
- Go to Account, then API Management, and create a new key of the system-generated type.
- Keep Enable Reading on and turn on Enable Spot & Margin Trading.
- Leave Enable Withdrawals off.
- Choose Restrict access to trusted IPs only and paste the server IP.
- Copy the API key and the secret key into the Resolutes dashboard. The secret is shown only once.
Where the key is stored
At Resolutes the key goes straight to a secrets vault in the cloud, encrypted, and is never stored in the database or shown again on the screen. Only the trading server can read it, and only to send orders.
Common mistakes
- Funds in the Funding wallet instead of Spot: the bot only trades the Spot wallet, so transfer the balance first.
- Copying the key with a missing character: paste it in full, without spaces.
- Creating the key without the IP lock: the engine refuses it and shows the reason in the dashboard.
How to disconnect
Deleting the key at the exchange cuts access immediately. You do not depend on the platform to stop: the control is always in your hands.



