Is it safe to connect your exchange API key to a portfolio tracker?
A read-only key cannot move your money, but it is not risk-free. Here is what it exposes and how to limit the damage if it leaks.
Connecting an exchange API key to a portfolio tracker is reasonably safe if the key is read-only: such a key cannot trade or withdraw, so a leak exposes your balances and history but not your funds. The real danger is a key created with trading or withdrawal permissions, or a key you forget about. Create a separate read-only key for each service, restrict it to known IP addresses where the service supports it, and delete it when you stop using the service.
What can a read-only API key do?
An API key is a pair of codes (a key and a secret) that lets a program act on your exchange account without your password. What it can do depends on the permissions you tick when you create it.
| Permission | What it allows | Does a tracker need it? |
|---|---|---|
| Read (Binance: Enable Reading; Coinbase: View; Kraken: Query Funds and similar) | See balances, orders, trade, deposit and withdrawal history | Yes |
| Trading (Binance: Enable Spot & Margin Trading; Coinbase: Trade) | Place and cancel orders | No |
| Withdrawal or transfer (Binance: Enable Withdrawals; Coinbase: Transfer; Kraken: Withdraw Funds) | Send funds out of the account | Never |
Permission names change from time to time, so read the labels on your exchange's API page when you create the key.
What are the risks of a read-only key?
Read-only is not the same as harmless:
- Privacy. Anyone with the key can see exactly what you hold and when you bought it. Combined with your email from a breach, that makes you a target for phishing or worse.
- Where the key is stored. Most trackers with exchange sync keep your keys on their servers so they can poll balances. Your security then depends on theirs.
- Misconfigured keys. The most common real loss is a key that was meant to be read-only but had trading enabled. A thief cannot withdraw with it, but can place trades on your account, for example buying an illiquid coin at a bad price.
- Forgotten keys. Old keys for services you no longer use stay valid until you delete them, unless the exchange expires them.
Why do withdrawal permissions matter so much?
A key with withdrawal permission is as powerful as your login for the purpose of moving money, without needing your password or two-factor code each time. Exchanges treat it accordingly: Binance requires you to apply an IP access restriction before withdrawals can be enabled on a key, and Kraken's documentation advises giving withdrawal permission only to keys that truly need to move funds, with strict IP whitelisting. A portfolio tracker is never such a service.
How does IP whitelisting help?
IP whitelisting (also called IP restriction or binding) tells the exchange to accept requests with this key only from the addresses you list. If the key leaks, it is useless from anywhere else. A tracker that syncs from its servers can only use it if it publishes the IP addresses its servers use; if it does not, you cannot whitelist, and the key works from any address.
How do I set up an API key for a tracker safely?
- Turn on two-factor authentication on the exchange account first, if it is not already.
- Create a new key for this one service. Do not reuse a key across services, so you can revoke one without breaking the others.
- Name it after the service, so you know later what it is for.
- Tick only the read permission. Leave trading, transfer and withdrawal unticked.
- Add an IP restriction if the service lists the IP addresses to allow.
- Paste the key only into the official app or site. Never send it by email or chat, and never share your account password or seed phrase with any tracker.
- Check the key list after setup to confirm its permissions are what you meant.
- Delete the key when you stop using the service, and review your keys every few months.
Can you skip API keys altogether?
Yes, by entering holdings by hand. You lose automatic balance updates and trade import, which matters if you trade a lot. If you mostly hold, updating a few numbers after each purchase is not much work, and there is nothing to leak.
cryptoc takes that approach: no exchange API keys, no wallet connection and no account. You enter the coin, the amount and optionally an average buy price and a note such as "Bybit", and the portfolio stays on your device. If you need automatic sync with exchanges, tax reports or CSV import, an API-based tracker is the better tool; just give it a read-only key. See also how to track a crypto portfolio manually.
Questions
Can someone steal my crypto with a read-only API key?
Not directly. A key with only read permission cannot withdraw or trade. It can still reveal your balances, trade history and deposit history, so a leak is a privacy problem, not a theft.
Which API permissions does a portfolio tracker need?
Read only. On Binance that is Enable Reading, on Kraken permissions such as Query Funds, on Coinbase the View scope. A tracker never needs trading, transfer or withdrawal permissions.
What is IP whitelisting for an API key?
It limits a key to requests from IP addresses you list, so a stolen key does not work from anywhere else. Binance requires an IP restriction before a key can have withdrawals enabled, and Kraken recommends strict IP whitelisting for keys that can withdraw.
Should I delete API keys I no longer use?
Yes. Delete the key on the exchange when you stop using a service, and review your key list from time to time. A key you forgot about is the one most likely to leak unnoticed.
Is there a way to track my portfolio without any API key?
Yes. Enter holdings by hand in a tracker or spreadsheet. You lose automatic updates but there is no key to leak at all.