How to connect Bitget to Pilotbot
Step-by-step: switch your Bitget account to Unified mode, reach the Advanced Merchant tier, create an API key with a passphrase and P2P read/write permissions, and paste all three secrets into Pilotbot — without withdrawal access.
Pilotbot Team
Author
On this page
- Step 1 — Switch the account to Unified mode
- Step 2 — Reach the Advanced Merchant tier
- Step 3 — Open API Management on Bitget
- Step 4 — Create a new API key
- Step 5 — Set a passphrase
- Step 6 — Enable P2P (read and write)
- Step 7 — Restrict access by IP (recommended)
- Step 8 — Copy the three secrets
- Step 9 — Paste the keys into Pilotbot
- Why three secrets?
- Related articles
Bitget is being finalized in Pilotbot. The connection is already prepared, but Bitget only opens its P2P API to accounts at the Advanced Merchant tier (medium seller level) and above. Until your account reaches this level, the Bitget tab in the Add Account window shows an "Integration in development" notification instead of the keys form. This guide is already relevant, so you can prepare your account in advance — when the tab opens, the steps will not change.
Connecting Bitget is slightly different from Binance and Bybit because Bitget signs every request with three secrets — an API key, a secret key, and a passphrase that you create yourself — and its P2P API only works in the new Unified account mode. The steps below configure all of this. The key allows the pricing layer to read the market and manage the prices of your ads; it can never withdraw funds because you never enable the withdrawal permission.
Follow the steps in order. Two things in Bitget cause issues if done out of sequence, and both are accounted for below: the account must be switched to Unified mode before creating the key, and the key itself needs specifically the P2P permission — not just Spot trading.
Step 1 — Switch the account to Unified mode
On Bitget, open Settings → Account Mode and select Unified Account (unified common wallet). Pilotbot manages ads via Bitget's new API, which only works in this mode.
Do this first. A key created while the account is still in Classic mode loses its P2P permissions the moment the mode is switched — and the error Bitget shows afterward ("Incorrect permissions") does not explain the reason. If you switch the mode first, the issue does not occur.
Step 2 — Reach the Advanced Merchant tier
Bitget only opens the P2P API starting from the Advanced Merchant tier and above. The requirements set by Bitget:
- a security deposit of 200 USDT (it is frozen as collateral, not spent),
- at least 10 completed P2P orders in the last 30 days,
- an order completion rate of 90%+ in the last 30 days,
- trades with at least 5 different counterparties,
- no disputes on orders.
To apply on Bitget: P2P → More → Merchant Application. Review usually takes up to 5 business days. You can complete the remaining steps once the account reaches the required tier.
Step 3 — Open API Management on Bitget
Log into Bitget, click on the profile icon, and open API Keys — or go directly to the Bitget API key management page. Create the key here, after changing the mode from Step 1, not before.
Step 4 — Create a new API key
Click Create API and select System-generated. Give the key a name you will recognize, such as Pilotbot.
Step 5 — Set a passphrase
Bitget will ask you to invent a Passphrase for the key. This is the third secret, separate from the secret key, and Bitget requires it in every request.
- Choose a passphrase at least 8 characters long, using only letters and numbers (Bitget does not accept symbols here).
- Save it immediately. If you forget it, Bitget cannot recover it — you will have to delete the key and create a new one.
You will need to enter this passphrase into Pilotbot along with the API key and secret key.
Step 6 — Enable P2P (read and write)
In the key permissions, enable P2P with read and write simultaneously.
- Read allows the system to see your ads and the market.
- Write allows the pricing layer to change the prices of ads and show/hide them.
Without write access, the system will be able to display your ads but will not be able to change anything. Leave the Withdrawal permission disabled — Pilotbot never needs it, and without it, the system cannot move your funds.
Step 7 — Restrict access by IP (recommended)
In the IP binding section, add the IP addresses provided by Pilotbot. This way, the key will only work from Pilotbot servers — this is the most secure setup. Pass the 2FA / email verification if Bitget requests it.
Step 8 — Copy the three secrets
Bitget will show your API key, secret key, and the passphrase you chose. Save all three immediately — the secret key is only shown once. If you lose it, you will have to create a new key.
Step 9 — Paste the keys into Pilotbot
Return to Pilotbot, open Add Account, select the Bitget tab, and paste the API key, secret key, and passphrase. Click Add.
As soon as the account gets access to the P2P API, your Bitget account will appear in the sidebar. Next, set your strategy via the AI agent and enable automation for your ads.
Why three secrets?
Binance and Bybit sign requests with two secrets (key + secret). Bitget adds a third — the passphrase — which you set yourself. This is why the Bitget tab has an extra field that other exchanges do not. If Bitget ever responds with "apikey/password is incorrect", the discrepancy is almost always in the passphrase, not the API key.