Connecting to BingX
To connect BingX to JetScalp, create an API key in your BingX account and enter it in the connection settings.
BingX issues a key pair:
- API Key — the API key identifier.
- Secret Key — the secret key used to sign requests.
In JetScalp the BingX connection has two sections: Spot (spot trading) and Futures (USDT-M perpetual futures). They share one key: Spot and Perpetual Futures trading permissions are enabled separately within the key.
1.Open API key management
Sign in on the BingX website and open API Management from the profile menu or on the BingX API keys page . Each main account or sub-account can keep up to 20 active API keys.
2.Create an API key
Click the button to create a new API key and enter a name, for example JetScalp. The name is only for you — to tell keys apart.
3.Configure permissions
JetScalp needs read access to account data (Read), Spot trading for the Spot section and Perpetual Futures trading for the Futures section. For both sections:
- Read
- Spot Trading
- Perpetual Futures Trading
- Universal Transfer
- Withdraw
If you trade on only one market, enable trading only for it and turn off the other section of the connection. Permission names may differ depending on the version of the BingX interface.
Important: JetScalp does not need the withdrawal permission (Withdraw) — do not enable it. JetScalp also does not use transfers between accounts (Universal Transfer) or sub-account management.
4.Restrict access by IP
Bind the key to the public IP address JetScalp connects to BingX from. Up to 20 IP addresses, separated by commas, can be bound to one key. If JetScalp works through a proxy, enter the IP address BingX sees when you connect through that proxy.
BingX automatically deletes a key with trading permissions that is not bound to an IP address if it makes no API calls for 14 consecutive days. Keys bound to an IP address and read-only keys do not expire.
If you do not know which IP to enter, find it out first: with a wrong IP, BingX rejects the connection.
5.Confirm creation and save the key
BingX asks you to confirm — usually with an email code and a Google Authenticator (2FA) code. After that BingX shows the API Key and Secret Key. Copy both keys right away.
Important: The Secret Key is shown only once. If it is lost, delete the key and create a new one.
6.Check the position mode (for futures)
JetScalp supports a BingX futures account only in One-way Mode.
If Hedge Mode is enabled in your BingX futures settings, the Futures section does not connect and JetScalp shows a message about it. Switch the position mode in the BingX settings and connect again.
The position mode is a setting of your BingX account; JetScalp does not change it.
7.Add the connection in JetScalp
Open Settings → Connections, click Add connection below the connection list and click the tile BingX. The connection appears in the list, and its settings appear on the right.
Fill in the connection settings:
| Field | Value |
|---|---|
| Name | The connection name in the list. By default it is the exchange or broker name; you can change it. |
| API Key | The API Key from BingX. |
| Secret Key | The Secret Key from BingX. |
| Proxy | A proxy from the list or None. See Proxy settings. |
BingX has two markets, so the connection settings have two sections — Spot and Futures, each with its own switch and state. Turn off the section of a market you do not trade: JetScalp will not connect to it, and the section's fields are kept.
8.Turn on the connection and check
Turn the connection on with the switch on the right of its row in the list. The state appears under the connection name: first connecting…, then connected. If the connection fails, the error text appears there — the full text is shown in the tooltip and in the header of the connection settings. For all states, see Connections.
Check that:
- BingX is connected.
- The account balance is shown.
- Open positions are shown.
- Orders are placed and canceled.
If the connection does not work
Invalid API Key or Secret Key
Check that both keys are copied completely and without extra spaces.
Insufficient permissions
If quotes and account information work but orders are not placed, check the key permissions: the Spot section needs Spot trading, the Futures section needs Perpetual Futures trading.
Hedge mode is enabled
If JetScalp reports that the BingX Perpetual account is in Hedge Mode, switch the position mode to One-way Mode (see step 6).
IP restriction
If the key has an IP restriction, make sure the IP address of the computer or proxy is in the allowed list.
API key deleted
Open BingX → API Management and make sure the key exists. BingX deletes a key with trading permissions that is not bound to an IP address after 14 days without API calls — create a new key and bind it to an IP if you can.
Security
Never share your API Key and Secret Key — not in chats or Telegram, not with support, not on forums, in screenshots or public repositories.
JetScalp does not need the withdrawal permission — do not enable it.
If the key may have reached anyone else, delete it in BingX right away and create a new one.