Read-Only API Key: Binance, Bybit, OKX and MT5

What a read-only API key can do and why it is safe: the permissions on Binance, Bybit and OKX, the MT5 investor password, IP binding and leaks.

Fresco-style painting of a padlocked strongbox with glass sides showing gold and gemstones inside, with a brass key lying beside it on a stone table

A read-only API key sees your balance, positions and trade history, but it cannot place orders, transfer or withdraw. That is why you can give one to a trading journal or a tax tool: even if it is stolen, it exposes data, not the account. Below: which permissions to keep on Binance, Bybit and OKX, what MetaTrader 5 gives instead of a key, when to bind a key to an IP address, and what to do if a key leaks.

What a read-only key can do

An API key is a pair of strings, the key and the secret. With them a program gets into your exchange account without your password and does whatever the key's permissions allow. There are three kinds of permission:

  • Read. Balances, positions, orders and trade history.
  • Trade. Place, change and cancel orders on your behalf.
  • Withdraw and transfer. Move money out of the account or between accounts.

A key that can trade already gives access to your money. If it is stolen from a service or from your computer, a stranger can trade on your account, and with withdrawal rights take the funds as well. Binance says it plainly: entering your keys into a third-party platform is a security risk.

A read-only key removes that risk. It still exposes data, though: your trade history and the size of your account. Give it only to services you trust, and give each one its own key.

Which permissions to keep: Binance, Bybit, OKX and MetaTrader 5

Each venue uses its own names. The diagram follows the help pages and documentation of the exchanges and MetaQuotes as of 8 October 2026. It isn't a screenshot: the screens differ by region and version.

A diagram of the permissions on four platforms. Binance, Edit restrictions screen: only Enable Reading ticked; Enable Spot & Margin Trading, Enable Margin Loan, Repay & Transfer, Enable Futures and Enable Withdrawals off. Bybit: Read-Only chosen, not Read-Write. OKX: only Read ticked; Trade and Withdraw off. MetaTrader 5: the investor password instead of the master one
What stays on in a read-only key. The option names are the exchanges' own.
WhereKeepLeave offHow a service checks it
BinanceEnable ReadingEnable Spot & Margin Trading, Enable Margin Loan, Repay & Transfer, Enable Futures, Enable Withdrawalsthe apiRestrictions request: enableReading = true, every other permission false
BybitRead-OnlyRead-Writethe query-api request: readOnly = 1
OKXReadTrade, Withdrawthe account/config request: perm = read_only
MetaTrader 5investor passwordmaster passwordno keys: the password itself sets the rights

If a journal or an analytics tool asks for trading or withdrawal rights, that is a reason to say no. Reading is all they need.

How to create the key on each exchange

Binance

First Binance wants three things: two-factor authentication (2FA), a deposit of any amount to your Spot wallet, and completed identity verification.

  1. Open API Management. Profile icon → Account → API Management.
  2. Create the key. Create API → System generated, name it and confirm with 2FA or a passkey.
  3. Save the secret. The Secret Key is visible only at creation; after that it is masked.
  4. Check the permissions. Edit restrictions: only Enable Reading is ticked. It is on by default.

Since 30 January 2023 a system-generated key with no IP restriction can only read. Binance enables withdrawals only on a key bound to IP addresses.

Bybit

Keys are created on the website only; the app can't do it. A new account may be blocked from creating keys for its first 48 hours.

  1. Open API Management. Profile icon at the top right → API.
  2. Create the key. Create New Key → System-generated API Keys → API Transaction, and name it.
  3. Choose Read-Only. The other option, Read-Write, allows trading.
  4. Tick the sections. For example, Unified Trading. A Read-Only key will only read them.
  5. Confirm and save the secret. Your Google Authenticator code, then the API Key and API Secret. The secret is shown once.

OKX

  1. Open the API section. Profile → API; on the website it may be called API and connections. Click Create API key.
  2. Fill in the form. A name, the account (main or a sub-account) and the key's purpose.
  3. Keep one permission: Read. Leave Trade and Withdraw off.
  4. Set a passphrase. It is the key's own password. You can't view it later: if you lose it, delete the key and create a new one.
  5. Save all three strings. API key, Secret key and Passphrase.

In some regions OKX lets you create a key only if the account holds more than $100. Residents of the European Economic Area and the US have their own OKX sites, and keys from them work through eea.okx.com and us.okx.com. Check that the service supports yours.

MetaTrader 5: the investor password

A MetaTrader 5 account has two passwords. The master password gives full rights. The investor password lets you view the account and analyze prices, but not trade. That is the one a journal gets instead of a key.

You can change the investor password in the terminal: Tools → Options → the Server tab → Change → Change investor password. If the broker forces a change of the master password, the investor password is reset too.

Should you bind the key to an IP address?

IP binding means the key accepts requests only from the addresses you list. Exchanges recommend it: a stolen bound key won't work from someone else's computer.

The rule is simple. If a service publishes its IP addresses, enter them. If it doesn't, a read-only key can stay unbound: it can't trade or withdraw anyway. But each exchange has its own limits for unbound keys.

ExchangeA key with no IP binding
BybitStops working after 90 days, or 7 days after you change the account password
BinanceDeleted after 30 days without use
OKXA key with Trade or Withdraw is deleted after 14 days without use

A service that uses the key all the time never hits Binance's 30-day rule. On Bybit, though, an unbound key stops working after 90 days. What to choose when you connect a journal on each exchange, and how to extend a Bybit key, is covered on our pages about connecting Binance, Bybit and OKX.

What to do if a key leaks

Bybit lists where a secret must never go: screenshots and videos, public source code and repositories, messages over insecure channels. If the secret may have reached someone else:

  1. Delete the key at once. On Binance in API Management, on Bybit with Delete in the Action column (website only), on OKX in the API section. A deleted key works for no one.
  2. Don't rely on a password change. On Bybit an unbound key keeps working for 7 days after you change the account password. Only deleting it switches it off.
  3. Check the history. Orders, trades, transfers and withdrawals over the last days. On OKX, the Security Center shows when keys with Trade or Withdraw and no IP binding were used.
  4. Create a new key. Read-only, and a separate one for each service, so a leak at one doesn't have to be fixed everywhere.
  5. Contact the exchange's support. If you see trades or withdrawals you didn't make.

A checklist before you hand over a key

  • One permission: read. Check it on the API page after the key is created, not only while creating it.
  • One key per service. Delete the one you no longer need without touching the rest.

A journal connected with a key records the trades itself, with fees, funding and MAE and MFE. If you keep your journal by hand, you need no key: the trading journal template for Excel is enough, and what to record is covered in How to Keep a Trading Journal.

Sources

Button names come from the exchanges' English sites. Other languages and regional sites may word them differently, and exchanges redesign their pages from time to time.

Share

Read next