Connect your tools.
Know their access.
Tracking a portfolio, syncing records and placing trades need different permissions. Start with what you want to do, then understand what the connection needs.
We have not seen a specific rate for this code on an official Binance page; any fee discount that applies is confirmed on Binance’s own pages and in your account.
Register on Binance ↗Referral link. We may earn a commission from qualifying use. Eligible users only.
No login · No API keys · Runs in your browser
This site explains connections. It does not connect to your account.
A portfolio tracker
asks for trading access. Why?
Separate reading, trading and withdrawals. Understanding each permission helps you compare what a tool requests with what you actually need.
Read the guide ↗Connection check
Choose a purpose to see the access you should review.
The connection library
All guides →Prices, portfolios or trades: do you need an API key?
Decide whether a task needs account access before connecting a third-party tool.
Read the guide ↗02 · Choosing API permissionsRead, trade and withdraw: what does each permission allow?
Compare a portfolio dashboard with a trading tool to understand access boundaries.
Read the guide ↗03 · Creating and configuring API keysConnecting a tool to the Binance API: four checks before you create the key
Check who and what the tool connects to, the key type and access it needs, what to record without secrets, and how you will revoke the key.
Read the guide ↗Connections need maintenance.
Key types, IP restrictions and interface changes can affect a working connection. Follow the official changes with these notes.
All guides (13)
- Prices, portfolios or trades: do you need an API key? ↗
- Read, trade and withdraw: what does each permission allow? ↗
- Connecting a tool to the Binance API: four checks before you create the key ↗
- API connection failed: checking -2015, -1021, -1022 and 429 ↗
- Leaving a trading tool: what to check after uninstalling ↗
- What data does a read-only connection leave behind? ↗
- Planned key rotation or immediate revocation? ↗
- Diagnosing -1021 and -1022 without exposing credentials ↗
- Pause on 429: coordinating retries behind a shared IP ↗
- Testnet shows different balances: check the environment first ↗
- Which IP belongs on a cloud tool’s allowlist? ↗
- HMAC, RSA or Ed25519: check tool compatibility first ↗
- Binance sub-account API keys: what can a connected tool touch?↗
- Binance user data stream disconnected: 24-hour limit, missed pong or retired listenKey?↗
- Binance API futures permission won’t enable: key created too early, Portfolio Margin, or no IP restriction?↗