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.

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.
| Where | Keep | Leave off | How a service checks it |
|---|---|---|---|
| Binance | Enable Reading | Enable Spot & Margin Trading, Enable Margin Loan, Repay & Transfer, Enable Futures, Enable Withdrawals | the apiRestrictions request: enableReading = true, every other permission false |
| Bybit | Read-Only | Read-Write | the query-api request: readOnly = 1 |
| OKX | Read | Trade, Withdraw | the account/config request: perm = read_only |
| MetaTrader 5 | investor password | master password | no 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.
- Open API Management. Profile icon → Account → API Management.
- Create the key. Create API → System generated, name it and confirm with 2FA or a passkey.
- Save the secret. The Secret Key is visible only at creation; after that it is masked.
- 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.
- Open API Management. Profile icon at the top right → API.
- Create the key. Create New Key → System-generated API Keys → API Transaction, and name it.
- Choose Read-Only. The other option, Read-Write, allows trading.
- Tick the sections. For example, Unified Trading. A Read-Only key will only read them.
- Confirm and save the secret. Your Google Authenticator code, then the API Key and API Secret. The secret is shown once.
OKX
- Open the API section. Profile → API; on the website it may be called API and connections. Click Create API key.
- Fill in the form. A name, the account (main or a sub-account) and the key's purpose.
- Keep one permission: Read. Leave Trade and Withdraw off.
- 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.
- 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.
| Exchange | A key with no IP binding |
|---|---|
| Bybit | Stops working after 90 days, or 7 days after you change the account password |
| Binance | Deleted after 30 days without use |
| OKX | A 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:
- 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.
- 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.
- 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.
- 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.
- 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
- Binance: How to Create API Keys on Binance?: the requirements, the steps, Enable Reading; since 30 January 2023 a key with no IP restriction can only read; withdrawals need an IP restriction.
- Binance: Frequently Asked Questions on API: the Secret Key is visible only at creation; third-party platforms are a security risk.
- Binance: How to Use an API Key Securely: unbound keys inactive for 30 days are deleted; one key per purpose; change a key at once if you suspect it is compromised.
- Binance Developers: Wallet Quick Start: a new key's default restriction is Enable Reading.
- Binance Developers: Margin Trading Best Practice: the Enable Spot & Margin Trading and Enable Margin Loan, Repay & Transfer permissions.
- Binance: How to Create an API Key for a Futures Lead Trading Portfolio?: the Edit restrictions button and the Enable Futures permission.
- Binance: How to Download and Set up Binance Gift Card API: the Enable Withdrawals permission.
- Binance Developers: Get API Key Permission: the apiRestrictions request and its fields.
- Bybit: How to Create Your API Key?: website only, 48 hours for a new account, the API Management steps.
- Bybit EU: What Is API Trading and How to Set It Up: Read-Only and Read-Write, IP whitelisting and No IP restriction, 90 days unbound, the secret shown once, where a secret must never go.
- Bybit API: Create Sub UID API Key: an unbound key stops working after 90 days, or 7 days after a password change.
- Bybit API: Get API Key Information: the query-api request and its readOnly field.
- Bybit: How to Delete Your API Key: Delete in the Action column, website only.
- OKX: API FAQ: creating a key, the passphrase, the $100 requirement, the EEA and US sites, expiry of keys with no IP binding.
- OKX API v5 documentation: the Read, Trade and Withdraw permissions; up to 20 IP addresses; 14 days for an unbound key with Trade or Withdraw; the Security Center; the account/config request and its perm field.
- MetaTrader 5 Help: Connect to an Account: the master and investor passwords and what investor access allows.
- MetaTrader 5 Help: Platform Settings: changing the investor password on the Server tab.
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.


