Binance API 权限回读与限制控制清单

决策矩阵

来源地图

• Binance Developer Docs：General REST API Information（binance-spot-rest-general）
• Binance Developer Docs：Get API Key Permission（binance-api-restrictions）
• Binance Support：How to Create an API Key（binance-api-key-faq）
• Binance Developer Docs：Sub Account API Key IP Restriction（binance-subaccount-ip-restriction）

控制说明

1. Permission readback

这一项要求读者把公开来源翻译成操作规则。这里的含义是：the permission endpoint is the evidence object for what the key is allowed to do。可执行动作是：record reading, trade, margin, futures, withdrawal and transfer fields before production use。仍然未知的是：account-specific restrictions, delayed UI changes and future API-field changes。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、安全保证、恢复保证、平台排名或价格暗示。

2. Timing security

这里的含义是：signed requests can fail or be replay-risky if timestamp and recvWindow handling is careless。可执行动作是：sync time, keep recvWindow narrow and log non-secret timing errors。仍然未知的是：network jitter, machine clock drift and exchange-side processing latency。

操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。

3. IP scope

这里的含义是：IP restrictions can reduce key misuse but can also lock out intended automation。可执行动作是：document trusted IPs, runtime host and emergency disable path。仍然未知的是：dynamic IP changes, NAT routing and sub-account exceptions。

操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。

4. Withdrawal boundary

这里的含义是：withdrawal permission has a different risk class from read or trade permission。可执行动作是：keep withdrawal disabled unless a separately reviewed workflow requires it。仍然未知的是：future account policy, address allowlist state and private support outcomes。

操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。

5. Vendor boundary

这里的含义是：a bot or third-party connector can hide which permissions it actually needs。可执行动作是：require a least-privilege permission list before key creation。仍然未知的是：vendor custody practices, logging, storage, breach history and revocation latency。

操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。

仍需明确的未知项

• account-specific restrictions, delayed UI changes and future API-field changes
• network jitter, machine clock drift and exchange-side processing latency
• dynamic IP changes, NAT routing and sub-account exceptions
• future account policy, address allowlist state and private support outcomes
• vendor custody practices, logging, storage, breach history and revocation latency

实用结论

Binance API key 应通过 permission readback、timing security 与 IP scope 审核，而不是只相信 bot setup screen。Binance developer documentation 说明 endpoint security types、signed requests、timestamp/recvWindow 控制，以及会返回 ipRestrict、enableReading、enableWithdrawals、enableSpotAndMarginTrading 等字段的 Get API Key Permission endpoint。可执行动作是在启用任何自动化流程前，记录 read、trade、transfer、withdrawal 与 IP restrictions。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、API key、池子路径、稳定币余额、代币化资产或政策框架在任何未来条件下都能成功的承诺。