Start
Connect an exchange with the narrowest useful permissions.
An exchange connection supplies market, balance, and order access. Configure it for the intended execution mode and keep withdrawal permission disabled.
Prepare the exchange account
- Enable account security. Turn on strong multi-factor authentication at the exchange before creating API access.
- Create a dedicated API key. Use a clear label such as Gimmer and avoid sharing the key with another bot.
- Grant trading access only. Enable spot and, only when required, margin permissions. Never enable withdrawals for Gimmer.
- Apply IP restrictions when practical. A stable egress IP can further limit where the key is usable.
- Record the credentials once. Enter them directly in the local desktop app and do not paste them into the public website.
Add the connection in Gimmer
Open Exchanges, choose the supported venue, and enter the fields requested by that connector. Some exchanges require an API key and secret; others can also require a passphrase, account mode, subaccount, or network selection.
Save the connection and use the available health or validation action. A saved credential is not necessarily a working credential.
| Failure | Likely checks |
|---|---|
| Authentication failed | Key, secret, passphrase, clock accuracy, account mode, and IP allowlist. |
| Permission denied | Spot or margin trading permission and exchange-specific account restrictions. |
| Insufficient balance | Free balance in the correct wallet, not total balance or another subaccount. |
| Minimum order failure | Exchange minimum quantity, notional value, precision, and fees. |
| Rate limit or unavailable | Pause retries, confirm exchange status, and preserve the exact error. |
Validate with low-risk steps
- Confirm that balances and markets load.
- Run a backtest that does not place exchange orders.
- Run simulation and observe at least one expected candle evaluation.
- If you choose live mode, start with a small amount and monitor the first order through a final status.
Revoke exposed keys
If a key or secret appears in a screenshot, log, chat, repository, or support message, revoke it at the exchange and create a new restricted key.