Kuidas ühendada börs BackFuture AI-ga: API võtmed, turvalisus ja ühenduse kontroll
BackFuture AI works through an börs ühendus via API. This means that the kasutaja’s vahendid remain on the börs account, while süsteem receives only the permissions that the kasutaja explicitly grants in the API võti.
Supported börsid
At the current stage, the platvorm is focused on working with MEXC and KuCoin. In the future, the list of ühendused can be expanded: Binance, OKX, Bitget, Gate.io, HTX, BingX, Coinbase, Bybit and other börsid.
General ühendus process
- The kasutaja logs into their börs account.
- Creates a new API võti.
- Disables väljavõtmise õigus.
- Enables only the required permissions: balance reading, order reading and kauplemine.
- Sets an IP restriction if the börs supports it.
- Copies the API Key and Secret Key.
- Adds the ühendus in the BackFuture AI dashboard.
- Runs a ühendus test.
- After a successful check, enables the required strateegia or bot.
Required API permissions
| Permission | Needed? | Miks |
|---|---|---|
| Read | ✅ Yes | So süsteem can see balances, orders, positions and staatus. |
| Trade | ✅ Yes | So the bot can open, add to and close tehingud. |
| Withdraw | ❌ No | This permission must not be given to a kauplemine bot. |
| Futures | ◐ If needed | Only for strateegiad that work with futures. |
| IP whitelist | ✅ Recommended | Restricts key usage to approved server IP addresses. |
Kuidas to name a ühendus correctly
In the dashboard, it is better to use clear ühendus names. This is especially oluline if the kasutaja has several börsid, sub-accounts or strateegiad.
- MEXC Spot Main — main spot account on MEXC.
- KuCoin Futures Conservative — futures account for a conservative strateegia.
- Recovery PRO Connection — separate ühendus for Recovery/PRO logic.
- BTC ETH New Groups — separate ühendus for new BTC/ETH grupid.
Step-by-step näide
Step 1. Create an API võti on the börs
In the börs account, open API Management or API Keys. Usually the börs asks for a key name and confirms the action through email, phone or 2FA.
Step 2. Set permissions
For a kauplemine ühendus, read and tehing permissions are usually needed. Withdrawal must be disabled. If the börs offers separate permissions for spot and futures, enable only the turg you really plan to use.
Step 3. Add the key to BackFuture AI
In the dashboard, the kasutaja selects an börs, enters API Key and Secret Key, sets a ühendus name and saves it. Secrets should not be displayed in full after saving.
Step 4. Test the ühendus
Süsteem checks the key, permissions, balance access and the ability to receive staatus. If everything is correct, the ühendus receives an “Online” or “Connected” staatus.
Step 5. Enable a strateegia
After the test, the kasutaja can select pairs, risk level, marginaal limit, lisaost behavior, Recovery Mode and other seaded.
Typical ühendus errors
| Error | Cause | Mis to do |
|---|---|---|
| Invalid key | API võti or secret was copied incorrectly. | Create a new key or copy the values again. |
| No kauplemine permission | Trade permission is disabled. | Enable kauplemine permission, but keep withdrawal disabled. |
| IP not allowed | IP restriction does not include the server IP. | Add the correct server IP to the börs whitelist. |
| Exchange unavailable | The börs API is temporarily unavailable. | Wait and run the test again. |
Security principles
- Never enable väljavõtmise õigus for bot API võtmed.
- Use separate API võtmed for different strateegiad.
- Use IP restrictions millal possible.
- Do not show API secrets in full after saving.
- Delete old keys if they are no longer used.
- Use 2FA on the börs account.
Kokkuvõte
The safest model is millal vahendid remain on the kasutaja’s börs, and BackFuture AI works only through limited API permissions. This allows the platvorm to automate kauplemine logic without direct access to withdrawals.