Connect Your Exchange API

Create a read-only API key on your exchange and paste it into Blave to see your balances and positions across exchanges on one page. Blave can't trade or withdraw with it.

Connecting an exchange API means giving Blave a read-only API key you created on your exchange, so Studio can read your balances and positions. Six exchanges are supported: Binance, OKX, BingX, Bitget, Bitunix and Bybit. The key only needs read permission — with it, Blave can't place orders or withdraw funds. Create the key on your exchange, then paste it on the Blave API page.

What do you get after connecting?

• Portfolio page: every connected exchange combined — account value over time, performance, allocation, and each coin's balance and exposure by exchange and wallet.
• The symbol picker on Studio charts gets a "Portfolio" tab listing the coins you currently hold, so you can switch charts without searching.
• Accounts Blave reads: Binance spot, USDⓈ-M futures and Simple Earn Flexible; the OKX trading account; BingX spot and perpetual futures; Bitget spot and futures on a classic account; Bitunix spot and futures; the Bybit Unified Trading Account. None of the six reads the Funding account — coins held there won't show on the Portfolio page.

Is it safe to give Blave an API key?

• Grant read permission only. Exchanges attach permissions to the key itself: whoever holds a read-only key can view the account but can't place orders, transfer or withdraw.
• Blave uses the key to read your balances and positions on a schedule — that's what builds the Portfolio page.
• The connect dialog includes the API Connection Policy: Blave collects and analyzes data from connected accounts in anonymized form to improve the product. To stop Blave reading your account, remove the key with the deletion steps.

How do you create a read-only API key on each exchange?

The flow is similar everywhere: open your account's API management page, create a key, give it read permission only, pass the security check, and copy the key. Two rules apply to every exchange:

• Leave the IP allowlist empty. If you bind your own IP, Blave's servers aren't on the list and can't read the account.
• Read only. Leave trading, transfer and withdrawal permissions off.

Binance｜OKX｜BingX｜Bitget｜Bitunix｜Bybit

Button and field names below follow each exchange's English website; they may differ in other languages or after a redesign.

Binance

Before you can create a key, Binance requires 2FA, a deposit of any amount to your Spot Wallet, and identity verification. Use a system-generated (HMAC) key; self-generated RSA/Ed25519 keys won't connect. Blave checks your USDⓈ-M futures account when connecting, so an account without futures enabled won't connect.

1. Log in to Binance on the web, click your profile icon → "Account" → "API Management", then click "Create API". In the app: "More" → "Other" → "API Management".
2. Choose "System-generated", enter Blave as the label, and complete 2FA.
3. Check that "Enable Reading" is the only permission (it's the default). Don't tick anything else or set an IP restriction.
4. Copy the API Key and Secret Key.

Binance official guide

OKX

1. Log in to OKX on the web, go to "Profile" → "API and connections", then click "Create API key".
2. Enter an API key name (for example, Blave) and under "Account" pick the account Blave should read.
3. Under "Permissions", tick "Read" only. Leave the IP address allowlist empty.
4. Set a Passphrase and write it down. OKX won't show it again — if you lose it, delete the key and create a new one. You'll need it when connecting on Blave.
5. Pass the security check, then copy the API Key and Secret Key.

OKX official guide

BingX

Blave checks your perpetual futures account when connecting, so an account without futures enabled won't connect.

1. Log in to BingX on the web, open "API Management" in your user center, then click "Create API".
2. Enter a name you'll recognize (for example, Blave) and pass the security check.
3. Keep read permission only: leave spot trading, futures trading, universal transfer, sub-account management and withdrawal off, and leave the IP empty. BingX doesn't delete read-only keys for inactivity.
4. Copy the API Key and Secret Key.

Open BingX API Management

Bitget

Only classic accounts are supported for now. A key from a Unified Trading Account (UTA) returns "Invalid API." when connecting.

1. Log in to Bitget on the web, open "API Management" in your personal center, then click "Create New API".
2. Enter Blave under "Notes" and set an API Passphrase. Write it down — you'll need it when connecting on Blave.
3. Set permissions to "Read-only" and don't bind an IP.
4. Enter the email, SMS and Google verification codes, then copy the API Key and Secret Key.

Bitget official guide

Bitunix

Blave checks your futures account when connecting, so an account without futures enabled won't connect.

1. Log in to Bitunix, click your profile icon → "API Management", then click "Create API".
2. Enter Blave under "Note" and set "Purpose" to "Bind Third-Party App" — permissions switch to "Read-only" automatically. If the screen looks different, what matters is granting read permission only.
3. Pass the security check. The API Key and Secret Key appear on screen — copy them right away.

Open Bitunix API Management

Bybit

New accounts may be unable to create keys for the first 48 hours. Use a system-generated (HMAC) key; self-generated RSA/Ed25519 keys won't connect. A Bybit key without an IP binding expires after 90 days — see troubleshooting to extend it.

1. Open Bybit on a computer (API keys can't be created in the app), then click your profile icon → "API" to reach the "API Management" page.
2. Click "Create New Key" and choose "System-generated API Keys".
3. Choose the usage the screen offers and enter Blave as the name.
4. Set permissions to "Read-Only" and choose "No IP restriction".
5. Enter your Google 2FA code, then copy the API Key and Secret Key.

Bybit official guide

Paste the key into Blave

What if the connection fails?

• "Invalid API." Blave couldn't read the account with this key. Check in order: the key was copied incompletely or with extra spaces; the wrong exchange is selected; the OKX or Bitget Passphrase is missing or wrong; the Binance or Bybit key is a self-generated RSA/Ed25519 key; futures aren't enabled on Binance, BingX or Bitunix.
• A Bitget key always returns "Invalid API." If your Bitget account is a Unified Trading Account (UTA), it can't be connected yet — Blave only supports classic accounts.
• "The API has already been connected." This exchange account is already connected to a Blave account — possibly another one of yours. Delete it on that account's API page first, then connect again.
• Bybit worked, then the data stopped. Bybit keys without an IP binding expire after 90 days. On Bybit's API Management page, click edit in the key's "IP Address Added" column, choose "No IP restriction", submit and verify. The key stays the same and gets another 90 days (Bybit's official FAQ).

How do you delete a key?

1. First, on the "Exchange" tab of the Blave API page, click "Delete" next to the key and confirm.
2. Then delete the same key on your exchange's API management page.

Keep this order. If you delete the key on the exchange first, the record on Blave isn't removed automatically.