Binance API permissions and privacy: what read, trade and withdrawal access allow
See what a third-party tool can read and do through the Binance API: read, trade and withdrawal permissions, which IP belongs on a cloud tool’s allowlist, and how to delete data a read-only connection leaves behind.
Binance API futures permission won’t enable: key created too early, Portfolio Margin, or no IP restriction?
When [Enable Futures] won’t tick or has vanished, separate a key older than the futures account, Portfolio Margin removing old permissions, and a key with no IP restriction.
Read the guide ↗02 · Choosing API permissionsBinance sub-account API keys: what can a connected tool touch?
A sub-account fences off a balance and cannot withdraw, yet a tool with trading access can still move everything inside it. Where the key is created, who can edit it, IP binding and the order for shutting it down.
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 ↗02 · Choosing API permissionsWhat data does a read-only connection leave behind?
Map portfolio data, cached copies and deletion requests separately from revoking the API credential.
Read the guide ↗02 · Choosing API permissionsWhich IP belongs on a cloud tool’s allowlist?
Trace the actual outbound connection before changing IP restrictions for a cloud portfolio tool.
Read the guide ↗