The read-only permission of the Binance API (shown as Enable Reading in the interface) can only read data. It cannot place orders, cancel orders or withdraw funds, which makes it suitable for market queries, balance reconciliation and authorizing third-party bookkeeping tools. To create a key, first sign in to the account area of the Binance Official Site; mobile users can also review existing keys in the Official Binance App, and iPhone users can follow the iOS installation guide. Keep in mind that a read-only key cannot move funds but can still reveal balances and trade history, so it remains sensitive information and should not be handed to others casually.
What the Read-Only Permission Can and Cannot Do
A: The read-only permission can query account balances, open orders, historical orders, trade details, deposit records and withdrawal records. It cannot create orders, cancel orders or start any withdrawal. When a Binance API key is created, only the reading permission is ticked by default; trading, withdrawal, futures and other permissions must be enabled manually.
The value of read-only access is that it separates "viewing data" from "moving funds". After a read-only key is given to a reporting tool, a bookkeeping app or a self-built script, an attacker who obtains the key still cannot transfer assets away or place orders on the market, so the damage is limited to privacy.
The table below compares the abilities of common permission types. Exact names and options follow what the Binance API management page currently shows:
| Permission type | Can query balances and records | Can place or cancel orders | Can withdraw | Main risk if leaked |
|---|---|---|---|---|
| Read only (Enable Reading) | Yes | No | No | Holdings and trading habits are exposed |
| Spot and margin trading | Yes | Yes | No | Malicious orders cause losses |
| Futures trading | Yes | Yes (futures account) | No | Malicious positions or liquidation |
| Allow withdrawals | Yes | Depends on other ticks | Yes | Assets transferred out directly |
The table shows that a read-only key carries the lowest risk of the four configurations. For scenarios that only need to look at data, read-only should be chosen first, instead of ticking every permission for convenience.
How Public Market Data Differs from a Read-Only Key
A: Public market endpoints need no key at all; a read-only key solves the problem of viewing your own account data. Binance market endpoints, such as the latest price, candlesticks, order book depth and 24-hour statistics, are public data that anyone can call without logging in.
Many beginners assume that querying prices also requires an API key, but a single HTTP request is enough. The command below queries the latest BTCUSDT price directly:
curl "https://api.binance.com/api/v3/ticker/price?symbol=BTCUSDT"
The response is a piece of JSON containing the trading pair name and the latest traded price. Only data tied to a personal account, such as balances, open orders and trade history, requires an API Key and a signed request.
| Item | Public market endpoints | Read-only key endpoints |
|---|---|---|
| API Key required | No | Yes |
| Signature required | No | Yes (HMAC-SHA256) |
| Data available | Prices, candlesticks, depth, trades | Balances, orders, trades, deposit and withdrawal records |
| Involves personal privacy | No | Yes |
| Typical use | Chart watching, market dashboards, strategy backtests | Reconciliation, bookkeeping, holdings monitoring |
Three Typical Uses of the Read-Only Permission
A: The three most common uses of a read-only key are balance reconciliation, holdings monitoring and authorizing third-party tools. None of the three requires access to funds; each only needs stable reading of account data.
Use 1: Balance Reconciliation
Balance reconciliation means checking the actual balances in a Binance account against your own ledger or spreadsheet, item by item. By reading the asset list through the read-only endpoint and adding up your own records of buys, sells, deposits and withdrawals, you can find missed fees, unrecorded transfers or trades you forgot to log.
Three numbers usually matter during reconciliation: available balance, frozen balance and valuation. Frozen balance comes from unfilled open orders; it is easy to overlook and often causes the ledger to differ from the data returned by the API.
Use 2: Holdings Monitoring
Holdings monitoring means pulling account assets on a schedule and multiplying them by public market prices to get a total valuation. Many personal dashboards, phone home-screen widgets and alert scripts work this way.
Such scripts only read data, so a read-only key is enough. Whether the script runs on a personal computer, a Raspberry Pi or a cloud server, trading permission does not need to be enabled.
Use 3: Authorizing Third-Party Bookkeeping and Tax Tools
Some bookkeeping, portfolio aggregation and tax preparation tools ask users for a read-only API key in order to sync trade history. These tools do not need to place orders, so read-only permission is sufficient; if a tool asks for withdrawal permission, authorization should stop immediately and the tool's source should be verified.
Step 1 to Step 4: Create a Read-Only API Key
A: Creating a read-only key generally takes four steps: sign in, open API management, create and name the key, then save the Secret and confirm the permissions. Menu positions on the Binance website and in the app may change between versions, so follow the page actually displayed.
Step 1: Sign In and Prepare Verification
First sign in to the Binance Official Site, confirm that the account has completed the required identity verification, and that two-factor authentication (2FA) is enabled. When an API key is created, Binance usually asks for confirmation through 2FA, email or an SMS code.
Step 2: Open the API Management Page
Find the "API Management" entry in the account center and choose to create a new API key. Binance lets the user choose the system-generated key type and enter a label for the key. A label that states the purpose, such as "read-only - bookkeeping tool", makes keys easier to tell apart later.
Step 3: Check Permissions and Bind an IP
After creation, the key page shows a permission list. A key for read-only use should keep "Enable Reading" on, and the trading, withdrawal and other permissions should be confirmed as off. It is also advisable to fill in an IP access restriction so that only your own server or fixed outbound address can call the API.
Step 4: Save the Secret Key
The API Key can be viewed on the page at any time, but the Secret Key is usually shown in full only once, at creation. Save the Secret immediately to a password manager or an encrypted file; do not send a screenshot to a chat group and do not write it into a public code repository. For specific storage options, see the article on how to store Binance API keys securely on this site.
The Basic Flow of Querying an Account with a Read-Only Key
A: A signed read-only request has three parts: the API Key goes in the request header, the parameters include a timestamp, and the signature is appended to the end of the query string. The signature is computed by applying HMAC-SHA256 to the parameter string with the Secret Key.
The Python example below reads the key from environment variables and then queries spot account information:
import os, time, hmac, hashlib, requests
API_KEY = os.environ["BINANCE_API_KEY"]
API_SECRET = os.environ["BINANCE_API_SECRET"]
query = f"timestamp={int(time.time() * 1000)}"
signature = hmac.new(API_SECRET.encode(), query.encode(), hashlib.sha256).hexdigest()
resp = requests.get(
f"https://api.binance.com/api/v3/account?{query}&signature={signature}",
headers={"X-MBX-APIKEY": API_KEY},
)
for item in resp.json()["balances"]:
if float(item["free"]) > 0 or float(item["locked"]) > 0:
print(item["asset"], item["free"], item["locked"])
The code prints only non-zero balances. If a request returns 401 or a permission error, first check whether the key has the reading permission ticked and whether the calling IP is on the whitelist. Other signing details are covered in the article on generating Binance API signatures on this site.
Common read-type endpoints include account information, open orders, order history, account trade records, deposit history and withdrawal history. Exact paths and parameters follow the official Binance API documentation.
How Balance Reconciliation Works in Practice
A: Balance reconciliation works by fixing a reconciliation point in time first, then checking the API data against your own records item by item. This avoids mismatches caused by data changing in real time.
The steps below suit individuals and small teams:
- Choose a reconciliation time, such as a fixed moment on the last day of each month, and record its timestamp.
- Read the available and frozen balances of each asset at that moment through the read-only endpoint.
- Read the trade records, deposit records and withdrawal records for the period.
- Take the previous closing balance, add the period's inflows and subtract the period's outflows to get the theoretical balance.
- Compare the theoretical balance with the actual balance returned by the API and check differences asset by asset.
When differences appear, the most common causes are fees deducted in another asset (for example paying with BNB), small-asset conversions, rewards credited from promotions, and unrecorded transfers between accounts (spot, funding, futures). Check asset by asset during troubleshooting instead of comparing everything combined.
| Source of difference | Typical symptom | How to investigate |
|---|---|---|
| Fee deduction | Balance slightly lower than expected | Check the fee asset in trade records |
| Transfers between accounts | Spot balance suddenly changes | Compare with transfer history |
| Promotional rewards and airdrops | Balance has one extra entry | Check funding records and announcements |
| Frozen balance | Available balance looks low | Query current open orders |
| Small-asset conversion | Several small assets disappear | Verify conversion records |
Risks and Security Notes When Using Read-Only Keys
A: A read-only key cannot cause funds to be transferred away, but it exposes holdings and trading behavior, so it must still be stored as a sensitive credential. If someone obtains holdings information, it can become material for social engineering and phishing scams.
Here are some basic security rules:
- Do not tick trading, futures or withdrawal permissions on a key meant for reading only; the fewer the permissions, the safer.
- Set an IP access restriction on the key so that only your own fixed address can call it.
- Use a separate key for each tool or script so that each can be revoked individually.
- Never send keys to anyone claiming to be support staff or a "managed trading" service; Binance officially never asks for a Secret Key.
- When abnormal calls appear or a tool is no longer used, delete the matching key at once on the API management page.
- If a third-party tool asks for withdrawal permission, treat it as a high-risk signal and refuse authorization.
Please also note that this site is an independent third-party tutorial site, not the official Binance website. API permission names, page entries and restrictions follow what the official Binance pages and documentation currently show. Crypto asset prices fluctuate sharply and investing carries risk; users in mainland China should learn and comply with local laws and regulations when using related services.
FAQ
Q: Can someone use a Binance API read-only permission to withdraw funds? A: No. The read-only permission does not include the ability to withdraw; withdrawals require the separate "Allow Withdrawals" permission. However, if a read-only key leaks, holdings and trade records can be seen, so the key should be deleted and recreated promptly.
Q: Do I need an API key just to check market prices? A: No. Public market endpoints such as the latest price, candlesticks and depth need neither a key nor a signature; sending an HTTP request is enough.
Q: Can a read-only key be used without an IP whitelist? A: It can, but this is not recommended. With an IP restriction, other addresses cannot use the key even if it leaks. Users with dynamic IPs can forward requests through a cloud server with a fixed outbound address.
Q: Can a read-only key see futures account data? A: A futures account usually requires futures-related options to be enabled separately in the key permissions before futures data can be read through the API. Exact options follow what the Binance API management page shows.
Q: A third-party bookkeeping tool asks for my read-only key. Is that safe? A: Read-only is relatively safe in terms of permissions, but confirm that the tool comes from a trustworthy source with a clear privacy statement, create a separate key for it, and delete the key when it is no longer used.
Q: What should I do if a read-only call returns a permission error? A: First confirm that the key has the reading permission ticked, then check whether the calling IP is on the whitelist and whether the system clock differs too much from Binance server time, and finally verify that the signature is correct.
Q: Does a read-only key need to be replaced regularly? A: Regular rotation is advisable, and the key should be replaced immediately after staff changes, when a tool is retired or when a leak is suspected. There is no universal rotation period; arrange it according to your own risk tolerance.
Anyone who does not yet have a Binance account can complete registration and verification through the Binance Official Site first and then create a read-only key following the steps in this article; on mobile, the Official Binance App can be installed to check key status at any time.