Cum conectezi un exchange la BackFuture AI: chei API, securitate și verificarea conexiunii
BackFuture AI works through an exchange conexiune via API. This means that the utilizator’s fonduri remain on the exchange account, while sistemul receives only the permissions that the utilizator explicitly grants in the cheie API.
Supported exchange-uri
At the current stage, the platformă is focused on working with MEXC and KuCoin. In the future, the list of conexiuni can be expanded: Binance, OKX, Bitget, Gate.io, HTX, BingX, Coinbase, Bybit and other exchange-uri.
General conexiune process
- The utilizator logs into their exchange account.
- Creates a new cheie API.
- Disables permisiune de retragere.
- Enables only the required permissions: balance reading, order reading and trading.
- Sets an IP restriction if the exchange supports it.
- Copies the API Key and Secret Key.
- Adds the conexiune in the BackFuture AI dashboard.
- Runs a conexiune test.
- After a successful check, enables the required strategie or bot.
Required API permissions
| Permission | Needed? | De ce |
|---|---|---|
| Read | ✅ Yes | So sistemul can see balances, orders, positions and status. |
| Trade | ✅ Yes | So the bot can open, add to and close tranzacții. |
| Withdraw | ❌ No | This permission must not be given to a trading bot. |
| Futures | ◐ If needed | Only for strategii that work with futures. |
| IP whitelist | ✅ Recommended | Restricts key usage to approved server IP addresses. |
Cum to name a conexiune correctly
In the dashboard, it is better to use clear conexiune names. This is especially important if the utilizator has several exchange-uri, sub-accounts or strategii.
- MEXC Spot Main — main spot account on MEXC.
- KuCoin Futures Conservative — futures account for a conservative strategie.
- Recovery PRO Connection — separate conexiune for Recovery/PRO logic.
- BTC ETH New Groups — separate conexiune for new BTC/ETH grupuri.
Step-by-step exemplu
Step 1. Create an cheie API on the exchange
In the exchange account, open API Management or API Keys. Usually the exchange asks for a key name and confirms the action through email, phone or 2FA.
Step 2. Set permissions
For a trading conexiune, read and tranzacție permissions are usually needed. Withdrawal must be disabled. If the exchange offers separate permissions for spot and futures, enable only the piață you really plan to use.
Step 3. Add the key to BackFuture AI
In the dashboard, the utilizator selects an exchange, enters API Key and Secret Key, sets a conexiune name and saves it. Secrets should not be displayed in full after saving.
Step 4. Test the conexiune
Sistemul checks the key, permissions, balance access and the ability to receive status. If everything is correct, the conexiune receives an “Online” or “Connected” status.
Step 5. Enable a strategie
After the test, the utilizator can select pairs, risc level, marjă limit, suplimentare behavior, Recovery Mode and other setări.
Typical conexiune errors
| Error | Cause | Ce to do |
|---|---|---|
| Invalid key | cheie API or secret was copied incorrectly. | Create a new key or copy the values again. |
| No trading permission | Trade permission is disabled. | Enable trading permission, but keep withdrawal disabled. |
| IP not allowed | IP restriction does not include the server IP. | Add the correct server IP to the exchange whitelist. |
| Exchange unavailable | The exchange API is temporarily unavailable. | Wait and run the test again. |
Security principles
- Never enable permisiune de retragere for bot chei API.
- Use separate chei API for different strategii.
- Use IP restrictions când possible.
- Do not show API secrets in full after saving.
- Delete old keys if they are no longer used.
- Use 2FA on the exchange account.
Concluzie
The safest model is când fonduri remain on the utilizator’s exchange, and BackFuture AI works only through limited API permissions. This allows the platformă to automate trading logic without direct access to withdrawals.