OKX 第三方应用 IP 白名单 API Key 清单
已验证事实边界
1. OKX says its Third Party App IP Whitelist limits API key usage to whitelisted broker servers when the broker supports the feature. 2. OKX tells brokers to provide public server IP addresses in IPv4, IPv6 or CIDR format for whitelisting. 3. OKX's user flow says users create an API key for the purpose of binding third-party apps and select a whitelisted third-party app from the dropdown. 4. OKX's API Guide says API keys can be bound to IP addresses and trade or withdraw keys not linked to IP addresses may expire after 14 days of inactivity. 5. OKX's API Agreement requires commercially reasonable security measures, including minimum permissions, MFA, encrypted storage, IP allowlisting where available and rotation after suspected compromise.
收起完整分析
决策矩阵
文章表格：可横向滑动，或聚焦表格区域后使用方向键。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Broker support | the IP whitelist flow depends on whether the third-party app or broker participates | confirm support in the OKX API creation flow before sharing any permission | whether a specific broker has changed its server IP list after publication |
| Public server IP | OKX asks brokers for public IPs, not internal private addresses | document broker egress IPs and reject vague infrastructure claims | whether the broker uses rotating NAT, proxy pools or cloud auto-scaling |
| Key purpose | the user flow distinguishes third-party app binding from ordinary self-managed API use | create a separate key for the broker and avoid reusing production trading keys | whether a user already granted broader permissions through an older key |
| Inactivity and expiry | OKX documents expiry behavior for trade or withdraw keys not linked to IP addresses | review stale keys before reconnecting automation | the user's private key usage logs and last authenticated call |
| Commercial boundary | the whitelist feature is a security control, not a revenue, safety or broker-quality claim | describe only the control flow and link to official OKX pages | broker solvency, app custody model and private user balances |
来源地图
- OKX：Third Party App IP Whitelist Launch（s1）
- OKX：OKX API Guide（s2）
- OKX：OKX API Agreement（s3）
- OKX：OKX API FAQ（s4）
- Bitget Support：API Key Terms of Use（s5）
控制说明
核对地区资格与账户条款
打开 →1. Broker support
这一项要求读者先把公开来源翻译成操作规则。这里的含义是：the IP whitelist flow depends on whether the third-party app or broker participates。可执行动作是：confirm support in the OKX API creation flow before sharing any permission。仍然未知的是：whether a specific broker has changed its server IP list after publication。因此本文不会把未知部分包装成安全承诺、收益承诺、官方背书、审批保证、可用性保证或注册诱导。
2. Public server IP
这里的含义是：OKX asks brokers for public IPs, not internal private addresses。可执行动作是：document broker egress IPs and reject vague infrastructure claims。仍然未知的是：whether the broker uses rotating NAT, proxy pools or cloud auto-scaling。
3. Key purpose
这里的含义是：the user flow distinguishes third-party app binding from ordinary self-managed API use。可执行动作是：create a separate key for the broker and avoid reusing production trading keys。仍然未知的是：whether a user already granted broader permissions through an older key。
4. Inactivity and expiry
这里的含义是：OKX documents expiry behavior for trade or withdraw keys not linked to IP addresses。可执行动作是：review stale keys before reconnecting automation。仍然未知的是：the user's private key usage logs and last authenticated call。
5. Commercial boundary
这里的含义是：the whitelist feature is a security control, not a revenue, safety or broker-quality claim。可执行动作是：describe only the control flow and link to official OKX pages。仍然未知的是：broker solvency, app custody model and private user balances。
仍需明确的未知项
- whether a specific broker has changed its server IP list after publication
- whether the broker uses rotating NAT, proxy pools or cloud auto-scaling
- whether a user already granted broader permissions through an older key
- the user's private key usage logs and last authenticated call
- broker solvency, app custody model and private user balances
实用结论
本文最有价值的地方是克制。OKX 的第三方应用 IP 白名单应被视为经纪商连接安全控制，而不是对任何应用的泛化背书。实用决策是核验所选 broker 是否支持 OKX 服务端 IP 白名单、API Key 是否按绑定第三方应用目的创建，以及最小权限、MFA、加密存储和泄露后轮换等 API Agreement 义务是否满足。 用户应获得一个更清楚的核验路径，而不是一个看似肯定、实则无法由公开证据承担的承诺。
相关专题与工具:开户与账户安全教程交易所 API 与行情数据核查
核对地区资格与账户条款
打开 →来源与证据
05- Third Party App IP Whitelist Launch · okx.com
- OKX API Guide · okx.com
- OKX API Agreement · okx.com
- OKX API FAQ · okx.com
- API Key Terms of Use · bitget.com