Monitoring a Binance account, read-only
You can watch a Binance account with Chartping using a view-only API key — it reads equity, margin and positions and warns you, but can't trade or withdraw. Here's how that works.
You can put a Binance account under watch with Chartping using a read-only API key: it reads your equity, margin and open positions and warns you as you approach the limits you set — and it can't place an order or move a coin. This is a plain-language explainer, not advice.
A read-only API key, nothing more
You create a view-only API key inside Binance, with trading and withdrawals left disabled, and paste it into Chartping. Binance is one of the exchanges where Chartping can prove a key's scope at connect — so if the key can trade or withdraw, it's rejected and never stored. The same holds for Bybit and Deribit. Keys are encrypted at rest (AES-GCM), and Chartping exposes no order or withdrawal endpoint of its own, so it couldn't act on your account even if it wanted to. More on the model on the read-only API keys page.
What it watches on an exchange account
Every snapshot, Chartping reads your account state — equity, margin level, margin usage, leverage and open positions — and checks it against your rules: daily loss, drawdown-from-peak and margin level, each with an early-warning threshold. Exchange accounts add four advanced controls on Pro — leverage, margin usage, concentration and equity floor. You set every number; Chartping never suggests one.
How the warnings reach you
As you approach a threshold you get an early warning; on a breach, a critical alert — by mobile push, SMS, a voice call or a signed webhook to Discord, Telegram, Slack or your own backend. Monitoring is snapshot-based and near-real-time, not tick-by-tick, and alerts are best-effort. If the connection drops, you get a fail-loud “monitoring stopped” alert rather than silence.
If a key ever gains trade rights
On the exchanges where scope is provable — Binance, Bybit and Deribit — a key that later gains trade or withdrawal rights stops the connection. Read-only isn't just checked once at setup; it's the standing condition for staying connected.
Beyond Binance
The same read-only approach covers 13 exchanges and brokers. Where scope can't be proven (OKX, Kraken, KuCoin and others) the key is accepted but hard-flagged, and Chartping still exposes no order or withdrawal path; broker tokens (OANDA, Alpaca, Tradier) are used strictly read-only; and Hyperliquid needs no key at all — it's watched from your public wallet address. See exchange & crypto account monitoring for the full list, or watch several accounts at once. It never trades.
Frequently asked
Does Chartping place trades on Binance?
No. Chartping connects with a read-only API key and exposes no order path at all. On Binance it proves the key's scope at connect and rejects any key that can trade or withdraw, so it can only read your account.
Do I have to give Chartping my Binance password?
Never. You create a view-only API key inside Binance yourself, with trading and withdrawals left off. Your Binance login and password never touch Chartping.
Can Chartping withdraw from my Binance account?
No. It has no withdrawal path, and on Binance a withdrawal-enabled key is rejected at connect. Keys are encrypted at rest (AES-GCM), and if a key later gains trade rights the connection stops.