How to Create a Bitget API Key Safely

Before you create the Bitget API key

An API key lets software send authenticated requests to an exchange account. It is not a wallet seed phrase, but incorrect permissions can still create serious risk. Complete these checks first:

Enable the available Bitget account-security methods before creating an API credential.
Choose a unique passphrase and keep it separate from your Bitget password.
Prepare the approved public IP address for the key restriction.

How to create a Bitget API key

01
Sign in to Bitget and open API Key Management.
02
Create a new API key and use a clear name that identifies its purpose.
03
Set and securely record the passphrase shown during creation.
04
Enable Read and Trade permissions for the required futures account only.
05
Bind the key to an IP address and keep Transfer and Withdraw permissions disabled.

Open the official Bitget API guide ↗

Recommended Bitget API permissions

ENABLERead and Trade

Only the access required to read the account and prepare or manage orders.

KEEP DISABLEDTransfer, Withdraw and access that is broader than required

Crypto Pulse never needs permission to remove assets from the exchange.

CREDENTIALSAPI key + Secret key + Passphrase

Copy credentials once, store them securely and never expose them in screenshots.

Bitget treats the API key, secret and passphrase as sensitive account credentials. Delete the key immediately in Bitget if any one of them may have been exposed.

How to connect the key to Crypto Pulse

Save your limits in Trading settings: order sizing, leverage, maximum positions, daily loss stop, slippage, margin mode and allowed markets.
Open Exchange API in the client portal and select the supported exchange.
Paste the dedicated API credentials and choose Verify connection.
Open an active signal and prepare an order preview. Check market, side, order amount, quantity, modeled risk, margin mode and slippage.

CURRENT STATUSIntegration planned

Live order submission is disabled. The current Binance flow verifies credentials and calculates previews only.

Bitget API key security checklist

Create a dedicated key instead of reusing a key from another bot or service.
Use the smallest possible permission set and keep withdrawals disabled.
Bind the key to approved IP addresses whenever the exchange supports it.
Never share an exchange password, 2FA code, seed phrase or wallet private key.
Delete and recreate the API key if a secret appears in a screenshot, message or log.
Review active keys regularly and remove credentials you no longer use.

Frequently asked questions

Which permissions should a Bitget trading API key have?

Use only Read and Trade. Keep Transfer, Withdraw and access that is broader than required disabled.

What Bitget credentials must be stored?

The connection uses API key + Secret key + Passphrase. Store them securely and never send them in chat or email.

Should withdrawal permission be enabled?

No. A trading integration does not need withdrawal permission. Crypto Pulse will never request it.

Can I connect Bitget to Crypto Pulse now?

Binance connection testing is available to eligible portal accounts. Bybit, OKX and Bitget remain planned integrations. Live order submission is currently disabled.