Saugus ryšys

Kaip prijungti biržą prie BackFuture AI: API raktai, saugumas ir ryšio patikra

BackFuture AI works through an birža ryšys via API. This means that the naudotojas’s lėšos remain on the birža account, while sistema receives only the permissions that the naudotojas explicitly grants in the API raktas.

Main saugumas rule: an API raktas for a prekyba bot must not have išėmimo leidimas. Only the permissions that are really needed for prekyba and būsena reading should be enabled.

Supported biržos

At the current stage, the platforma is focused on working with MEXC and KuCoin. In the future, the list of ryšiai can be expanded: Binance, OKX, Bitget, Gate.io, HTX, BingX, Coinbase, Bybit and other biržos.

General ryšys process

The naudotojas logs into their birža account.
Creates a new API raktas.
Disables išėmimo leidimas.
Enables only the required permissions: balance reading, order reading and prekyba.
Sets an IP restriction if the birža supports it.
Copies the API Key and Secret Key.
Adds the ryšys in the BackFuture AI dashboard.
Runs a ryšys test.
After a successful check, enables the required strategija or bot.

Required API permissions

Permission	Needed?	Kodėl
Read	✅ Yes	So sistema can see balances, orders, positions and būsena.
Trade	✅ Yes	So the bot can open, add to and close sandoriai.
Withdraw	❌ No	This permission must not be given to a prekyba bot.
Futures	◐ If needed	Only for strategijos that work with futures.
IP whitelist	✅ Recommended	Restricts key usage to approved server IP addresses.

Kaip to name a ryšys correctly

In the dashboard, it is better to use clear ryšys names. This is especially svarbu if the naudotojas has several biržos, sub-accounts or strategijos.

MEXC Spot Main — main spot account on MEXC.
KuCoin Futures Conservative — futures account for a conservative strategija.
Recovery PRO Connection — separate ryšys for Recovery/PRO logic.
BTC ETH New Groups — separate ryšys for new BTC/ETH grupės.

Step-by-step pavyzdys

Step 1. Create an API raktas 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 prekyba ryšys, read and sandoris permissions are usually needed. Withdrawal must be disabled. If the birža offers separate permissions for spot and futures, enable only the rinka you really plan to use.

Step 3. Add the key to BackFuture AI

In the dashboard, the naudotojas selects an birža, enters API Key and Secret Key, sets a ryšys name and saves it. Secrets should not be displayed in full after saving.

Step 4. Test the ryšys

Sistema checks the key, permissions, balance access and the ability to receive būsena. If everything is correct, the ryšys receives an “Online” or “Connected” būsena.

Step 5. Enable a strategija

After the test, the naudotojas can select pairs, rizika level, marža limit, papildymas behavior, Recovery Mode and other nustatymai.

Typical ryšys errors

Error	Cause	Kas to do
Invalid key	API raktas or secret was copied incorrectly.	Create a new key or copy the values again.
No prekyba permission	Trade permission is disabled.	Enable prekyba 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 išėmimo leidimas for bot API raktai.
Use separate API raktai for different strategijos.
Use IP restrictions kada 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.

Išvada

The safest model is kada lėšos remain on the naudotojas’s birža, and BackFuture AI works only through limited API permissions. This allows the platforma to automate prekyba logic without direct access to withdrawals.