Skip to content
Security guide

How to create a Binance read-only API key

Use the smallest possible permission set for portfolio tracking. The interface varies by Binance region, but the security rule does not: reading on, every asset-moving permission off.

Reading onlyNo tradingNo withdrawalsReview regularly

Before you create the key

An API key and secret act like credentials. A read-only configuration limits their power, but they still deserve careful handling.

Use a dedicated key

Create a separate key for portfolio viewing. Do not reuse credentials from a trading bot or another service.

Reading only

A balance tracker needs permission to read account data—not permission to place orders, transfer funds, or withdraw.

Review before saving

Confirm every trading, margin, futures, universal-transfer, and withdrawal switch remains disabled.

Treat the secret as sensitive

Do not email, message, screenshot, or publish the secret. Binance may show it only once during creation.

Revoke when unused

Remove keys you no longer use and revoke one immediately if you suspect that it was exposed.

Check Binance documentation

Menus and regional availability change. Verify the current interface and restrictions in Binance’s official documentation.

Step-by-step setup

  1. 1

    Open Binance API Management

    Sign in through the official Binance website, open your account settings, and locate API Management. Menu names can vary by region.

  2. 2

    Create and name a new key

    Choose the standard account API option available to you, complete Binance security verification, and give the key a recognizable name such as Portfolio Tracker.

  3. 3

    Set the restrictions

    Enable reading only. Keep Spot and Margin Trading, Futures, Universal Transfer, withdrawals, and any other asset-moving permission disabled.

  4. 4

    Copy the key and secret safely

    Copy the values directly into the app. Avoid saving the secret in notes, chat, email, screenshots, or unencrypted documents.

  5. 5

    Test and compare balances

    Connect the key and compare the resulting Spot and eligible Simple Earn balances with Binance before relying on the view.

  6. 6

    Review and revoke

    Periodically review active keys in Binance. Revoke this key when you stop using portfolio sync or if you suspect exposure.

Stop if you see these permissions

A portfolio viewer does not need control of your assets

Do not enable trading, margin trading, futures, withdrawals, transfers, or any permission that can place an order or move funds. Crypto Portfolio Tracker only needs the account-reading access required to retrieve supported balances.

After connecting

  • Compare the first imported balance with Binance.
  • Keep official Binance records for trades and taxes.
  • Review the key in Binance API Management periodically.
  • Remove the in-app connection before revoking the key.

If the secret is exposed

  1. Revoke the key in Binance immediately.
  2. Remove the corresponding connection from the app.
  3. Review Binance security and account-access logs.
  4. Create a new dedicated read-only key only if needed.

Binance is a trademark of its respective owner. This independent guide is not endorsed by or affiliated with Binance. For more detail, read the site’s security page.

Frequently asked questions

Which Binance permissions should a portfolio tracker have?

Reading only. Trading, margin, futures, transfers, and withdrawals should remain disabled. If an unrelated tracker demands asset-moving permission, do not connect it.

Should I reuse an API key from a trading bot?

No. Create a separate key with the minimum permissions required for each service. This makes the key easier to audit and revoke without interrupting other tools.

Why does my Binance key fail to connect?

The key may be inactive, expired, revoked, restricted by region or IP settings, or missing read access. Check Binance’s error message and current API settings; never enable trading or withdrawal access as a workaround.

Can a read-only key eliminate every risk?

No. It substantially limits what the credential can do, but account and portfolio information is still sensitive. Protect the secret, review permissions, and revoke it if exposed.