SHARKRULE / Learn

Bitget API setup: access, permissions and security

Understand Bitget account access before connecting any automation. These instructions explain the provider’s setup process; a SharkRule connection for this exchange is planned.

SharkRule · Reviewed

Check availability before creating a key

Bitget is on SharkRule’s roadmap and is not available in the current dashboard. This guide explains the provider’s access and permissions. Wait until your dashboard offers the connection before creating or sharing credentials.

Confirm that Bitget and the relevant product are available for your location and account. Use only the server IP shown in SharkRule’s authenticated connection guide for an IP allowlist; your phone or home-router IP is not the hosted trading server.

Create a dedicated HMAC key

  1. Open https://www.bitget.com/account/newapi in your browser and sign in. On a phone, use the browser’s desktop-site option if API management is unavailable in the mobile layout. Complete Bitget’s own security checks.
  2. Confirm the selected account is UTA. Do not change account mode without understanding its effect on existing balances and positions. Classic accounts are not supported by this connection.
  3. Choose Create API and the system-generated HMAC option, rather than an RSA key. Give it a recognizable name such as SharkRule. Set a new API passphrase; this is separate from your login password.
  4. Select Read and write and Unified account trade (uta_trade). Allow the account reading required for balances. Leave withdrawals, transfers and unrelated permissions disabled. Apply the server IP restriction shown in SharkRule.
  5. Complete verification and store the API key, secret key and chosen passphrase securely. Do not put them in screenshots, messages or this article. If the secret or passphrase is lost, create a replacement key.

Understand the permission boundary

UTA trading permission can cover more products than Spot at Bitget. SharkRule’s prepared adapter submits Spot orders only; that software restriction does not turn the exchange credential into a Spot-only credential. Avoid granting account-management write permissions or enabling borrowing just to make a connection pass.

When the connection becomes available

Your dashboard will show the supported account type, credential fields and server IP when this connection is available. Follow those instructions then. Verifying a connection and approving a trading strategy are separate steps; reading this guide never activates trading.

Resolve errors without widening access

Authentication errors often mean a mismatched secret, missing passphrase, wrong account type or incorrect IP allowlist. Copy values from the same HMAC key and check that UTA trading is enabled. Do not enable withdrawals to repair an error. A demo key is not interchangeable with this prepared live connection.

If an order status is uncertain, inspect order history directly at Bitget and allow reconciliation. Do not repeatedly activate replacement rules while a submission may already have been accepted.

Remove access at the provider

Review active orders directly at Bitget. Delete the dedicated API key or revoke the API-wallet approval through its official settings to remove that access. Revocation does not sell holdings or undo orders already accepted. If credentials are exposed, revoke promptly and review the account’s activity.

Frequently asked questions

Can I use Bitget Wallet instead?

No. This guide connects a Bitget exchange UTA account. It never needs a wallet recovery phrase.

Why is my passphrase rejected?

Use the API passphrase chosen for that key, not the login password. A lost passphrase requires a new key.

Official documentation and references

Prepared with AI assistance from the linked official documentation. Examples are hypothetical; no live account tests or return comparisons were performed.