Connect Binance with the right API permissions
Connect Binance using an API key and secret created in Binance API Management. Match production or testnet credentials to the environment you select. Enable reading and only the spot or futures trading permission your task requires; leave withdrawals disabled. A verified connection does not guarantee order execution or prevent trading losses.
Before you start
- A Binance account eligible for the selected market and API access.
- An active KLINEO entitlement and an available connection slot for the chosen mode.
- For sandbox testing, keys from the matching Binance spot or USDⓈ-M futures test environment.
Prepare the key at Binance
- Open Binance API Management on the official website. Create a system-generated API key and give it a label you can identify later.
- Enable reading and the trading permission for the market you actually intend to use. Do not enable withdrawals. Review the exchange’s available IP restrictions rather than weakening account protections to bypass an error.
- Save the API key and secret securely. KLINEO needs the API credentials, never your Binance login password. Do not send the secret to support or put it in screenshots.
Choose production or the matching testnet
KLINEO Virtual trading and an exchange sandbox are different concepts. Sandbox credentials do not authorize production trading, and a production key should not be used as if it were a sandbox key.
| Intended task | Credential source | Check before saving |
|---|---|---|
| Live spot | Binance production API Management | Production environment and spot trading access. |
| Live USDⓈ-M futures | Binance production API Management | Eligible futures account and futures permission; enable and test futures in KLINEO. |
| Spot sandbox verification | Binance Spot Test Network | Sandbox key and spot testnet context. |
| Futures sandbox verification | Binance futures test environment | Sandbox key and the matching USDⓈ-M futures context. |
Add and verify the connection in KLINEO
- Open Settings, find the exchange connections area and choose Connect exchange. Select Binance.
- Choose the intended environment. Paste the API key and secret into their separate fields, then submit the connection verification.
- Wait for a successful verification result. Read any account-identity or permission error before retrying; a saved record is not the same as a healthy connection.
- If using futures, enable futures on that connection and run its futures verification. Check the margin and position mode shown for the intended account.
- Open the intended product and confirm its exchange, pair, market and mode before placing or enabling any order.
Resolve common connection and order problems
- Invalid credentials or signature: check the copied key and secret, environment and whether Binance has restricted or deleted the key.
- Permission failure: check reading and the specific market permission. Do not turn on withdrawals to solve a trading error.
- Insufficient balance: check free balance in the correct exchange account. KLINEO simulated funds are not Binance production funds.
- Minimum amount or precision rejection: use the symbol’s current quantity, price-step and notional rules; these vary by market.
- Timeout or unknown order status: inspect Orders and Binance before resubmitting. A timeout does not establish that an exchange rejected the order.
- Unavailable account, market or region: follow the exchange’s eligibility rules. A KLINEO plan does not override them.
Stop using or revoke a Binance connection
- Inspect running bots, workflows, open orders and positions. Use their stop controls and check the resulting exchange state.
- In KLINEO Settings, use Revoke to retire the saved connection. Reconcile active work first if the action is blocked.
- In Binance API Management, delete or revoke the API key if you no longer need it, or immediately if you suspect it has been exposed.
- Verify open orders and positions directly at Binance. Removing an API key or KLINEO connection is not a position-closing instruction.