Kā pieslēgt biržu BackFuture AI: API atslēgas, drošība un savienojuma pārbaude
BackFuture AI works through an birža savienojums via API. This means that the lietotājs’s līdzekļi remain on the birža account, while sistēma receives only the permissions that the lietotājs explicitly grants in the API atslēga.
Supported biržas
At the current stage, the platforma is focused on working with MEXC and KuCoin. In the future, the list of savienojumi can be expanded: Binance, OKX, Bitget, Gate.io, HTX, BingX, Coinbase, Bybit and other biržas.
General savienojums process
- The lietotājs logs into their birža account.
- Creates a new API atslēga.
- Disables izņemšanas atļauja.
- Enables only the required permissions: balance reading, order reading and tirdzniecība.
- Sets an IP restriction if the birža supports it.
- Copies the API Key and Secret Key.
- Adds the savienojums in the BackFuture AI dashboard.
- Runs a savienojums test.
- After a successful check, enables the required stratēģija or bot.
Required API permissions
| Permission | Needed? | Kāpēc |
|---|---|---|
| Read | ✅ Yes | So sistēma can see balances, orders, positions and statuss. |
| Trade | ✅ Yes | So the bot can open, add to and close darījumi. |
| Withdraw | ❌ No | This permission must not be given to a tirdzniecība bot. |
| Futures | ◐ If needed | Only for stratēģijas that work with futures. |
| IP whitelist | ✅ Recommended | Restricts key usage to approved server IP addresses. |
Kā to name a savienojums correctly
In the dashboard, it is better to use clear savienojums names. This is especially svarīgi if the lietotājs has several biržas, sub-accounts or stratēģijas.
- MEXC Spot Main — main spot account on MEXC.
- KuCoin Futures Conservative — futures account for a conservative stratēģija.
- Recovery PRO Connection — separate savienojums for Recovery/PRO logic.
- BTC ETH New Groups — separate savienojums for new BTC/ETH grupas.
Step-by-step piemērs
Step 1. Create an API atslēga on the birža
In the birža account, open API Management or API Keys. Usually the birža asks for a key name and confirms the action through email, phone or 2FA.
Step 2. Set permissions
For a tirdzniecība savienojums, read and darījums permissions are usually needed. Withdrawal must be disabled. If the birža offers separate permissions for spot and futures, enable only the tirgus you really plan to use.
Step 3. Add the key to BackFuture AI
In the dashboard, the lietotājs selects an birža, enters API Key and Secret Key, sets a savienojums name and saves it. Secrets should not be displayed in full after saving.
Step 4. Test the savienojums
Sistēma checks the key, permissions, balance access and the ability to receive statuss. If everything is correct, the savienojums receives an “Online” or “Connected” statuss.
Step 5. Enable a stratēģija
After the test, the lietotājs can select pairs, risks level, marža limit, papildināšana behavior, Recovery Mode and other iestatījumi.
Typical savienojums errors
| Error | Cause | Kas to do |
|---|---|---|
| Invalid key | API atslēga or secret was copied incorrectly. | Create a new key or copy the values again. |
| No tirdzniecība permission | Trade permission is disabled. | Enable tirdzniecība permission, but keep withdrawal disabled. |
| IP not allowed | IP restriction does not include the server IP. | Add the correct server IP to the birža whitelist. |
| Exchange unavailable | The birža API is temporarily unavailable. | Wait and run the test again. |
Security principles
- Never enable izņemšanas atļauja for bot API atslēgas.
- Use separate API atslēgas for different stratēģijas.
- Use IP restrictions kad possible.
- Do not show API secrets in full after saving.
- Delete old keys if they are no longer used.
- Use 2FA on the birža account.
Secinājums
The safest model is kad līdzekļi remain on the lietotājs’s birža, and BackFuture AI works only through limited API permissions. This allows the platforma to automate tirdzniecība logic without direct access to withdrawals.