Connecting to Bitget
To connect Bitget to JetScalp, create an API key in your Bitget account and enter it in the connection settings.
Bitget issues three values:
- API Key — the API key identifier.
- Secret Key — the secret key used to sign requests, generated by Bitget.
- Passphrase — a passphrase you set yourself when creating the key.
Official guide: Bitget API Quick Start .
1.Open API key management
Log in to Bitget and open API key management . Keys are managed only in the Bitget web version — the mobile app no longer offers this.
2.Create an API key
Click Create API Key and choose System-generated API Key (HMAC). Enter a name for the key, for example JetScalp.
3.Set a passphrase
Bitget asks you to set a Passphrase — a password you make up yourself, for example MyJetScalp2026. Save it together with the API Key and Secret Key.
Important: The Passphrase cannot be recovered. If you forget it, delete the API key and create a new one.
4.Configure permissions
| Permission | Description |
|---|---|
| Read-Only | Reading account and market data. |
| Trade | Placing and canceling orders. |
| Transfer | Transfers between accounts. |
| Withdraw | Withdrawing funds. |
For JetScalp, enable:
- Read
- Trade
- Transfer
- Withdraw
Important: JetScalp does not need the withdrawal (Withdraw) and transfer (Transfer) permissions — do not enable them.
5.Restrict access by IP
Bitget recommends binding the API key to an IP address (IP Whitelist). Enter the public IP address JetScalp connects to Bitget from. If JetScalp works through a proxy, enter the IP address Bitget sees when you connect through that proxy.
If you do not know which IP to enter, find it out first: with a wrong IP, Bitget rejects the connection.
6.Confirm creation and save the key
Click Next / Confirm and confirm with an email, SMS or Google Authenticator code, whichever Bitget asks for. Bitget then shows the API Key, Secret Key and Passphrase. Save all three values right away.
7.Check the position mode (for futures)
JetScalp supports a Bitget futures account only in One-way Mode.
Bitget futures use Hedge Mode by default. Switch it before turning on the Futures section.
If the account is in hedge mode, the Futures section does not connect and JetScalp shows this message:
Bitget Futures: the account is in hedge mode (hedge_mode). JetScalp supports only one_way_mode — switch the position mode in the Bitget settings. Connection stopped.JetScalp trades USDT-M and USDC-M futures and checks the mode of both on connect, even without positions: Hedge Mode in either of them stops the whole Futures section. Switch both to One-way Mode, even the one you do not trade.
To switch the mode, open the Bitget futures trading page and select One-way Mode in the position mode settings. The mode is set separately for each futures type and cannot be changed while you have open positions.
The position mode is a setting of your Bitget account; JetScalp does not change it.
8.Add the connection in JetScalp
Open Settings → Connections, click Add connection below the connection list and click the tile Bitget. 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 Bitget. |
| Secret Key | The Secret Key from Bitget. |
| Passphrase | The Passphrase you set when creating the API key in Bitget. |
| Proxy | A proxy from the list or None. See Proxy settings. |
Bitget 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.
9.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:
- Bitget 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.
Invalid Passphrase
The Passphrase must exactly match the one you set when creating the key. A forgotten Passphrase cannot be recovered — delete the key and create a new one.
Insufficient permissions
If quotes and account information work but orders are not placed, check that the key has the Trade permission.
Hedge mode is enabled
If JetScalp reports that the Bitget Futures account is in hedge_mode, switch the position mode to One-way Mode (see step 7).
IP restriction
If the key has an IP restriction, make sure the IP address of the computer or proxy is in the allowed list.
RSA key used
Bitget supports system-generated HMAC keys and user-generated RSA keys. JetScalp works only with HMAC keys: an RSA key will not work — create a System-generated API Key (HMAC).
Security
Never share your API Key, Secret Key and Passphrase — 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 Bitget right away and create a new one.