Client onboarding · All teams · Sep 21, 2026 · 2 min read
How clients can create view-only exchange API keys safely
A plain-language guide to share with clients: what a read-only key is, which permissions to leave off, and how to store and revoke it.
By ChainLedger editorial team · Crypto audit, tax and fund reporting · Last reviewed
Key takeaways
- A view-only key can read balances and history but can't trade or withdraw.
- Leave trading and withdrawal permissions switched off, every time.
- Keys can be revoked at any time from the exchange's settings.
An API key lets software read an exchange account without logging in as the user. Exchanges let the account owner choose exactly what each key can do. For reporting and audit, the key only ever needs to read.
What the permissions mean
| Permission | What it allows | Needed for reporting? |
|---|---|---|
| Read / View | See balances, trades, deposits and withdrawals | Yes |
| Trade | Place and cancel orders | No, leave off |
| Withdraw / Transfer | Move funds out of the account | No, never enable |
| Manage account / Sub-accounts | Change settings or create keys | No, leave off |
Steps to share with clients
- 1Log in to the exchange on its official website and open the API management page, usually under security or settings.
- 2Create a new key and give it a clear label, such as "Accounting firm - read only".
- 3Tick only the read or view permission. Leave trade, withdraw and transfer unticked.
- 4If the exchange offers IP restrictions, add the addresses provided by the firm.
- 5Complete the exchange's security check, such as two-factor authentication.
- 6Copy the key, the secret and, if shown, the passphrase. Some exchanges show the secret only once.
- 7Share them through a secure channel the firm provides, not by plain email or chat.
Wallets don't need keys at all
For self-custody wallets, the public address is enough to read the full history. Nothing needs to be installed or approved, and ownership can be proven separately by signing a message from the wallet.
Revoking a key
The client can delete the key at any time from the same API management page, which immediately stops access. It's good practice to review keys at the end of an engagement and remove any that are no longer needed.
ChainLedger only asks for view-only keys and shows clients exactly which permissions to leave off.
Common questions
No. If only the read or view permission is enabled, the key can see activity but can't place trades or withdraw.
Related product page: Wallet and exchange integrations