加密平台私有 API 错误码披露雷达
本文正文暫以英文原文展示,翻譯版本需完成來源複核後再發布。
已验证事实边界
1. Bybit V5 Error Codes documentation includes permission and API-key-expiry labels suitable for non-secret incident classification. 2. Bybit V5 Rate Limit Rules documentation provides a source for rate-limit classification and retry budgeting. 3. Coinbase List Accounts API reference documents an authenticated account endpoint using authorization. 4. Coinbase Advanced Trade WebSocket documentation describes authenticated WebSocket setup and subscription surfaces. 5. OKX API documentation describes private WebSocket login and subscription controls that should be treated as venue-specific session evidence. 6. These sources do not prove private account eligibility, support recovery, live order safety, compliance status, regional access, uptime or future endpoint availability.
收起完整分析
决策矩阵
文章表格:可橫向滑動,或聚焦表格區域後使用方向鍵。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Error taxonomy | a code is useful only when mapped to documented meaning | record public source, exact code label and endpoint class | whether the same code has product-specific meanings |
| Retry class | rate-limit and permission failures require different recovery paths | separate backoff, credential review, permission review and hard stop cases | whether the original request already changed account state |
| Permission scope | private endpoints can fail because the key, account or product scope is wrong | map key permission and account surface before retrying | whether support-side status changes the diagnosis |
| Non-secret evidence | incident records must not leak credentials or account balances | store endpoint name, non-secret code, timestamp, source URL and stop rule | whether a screenshot contains private account data |
| Radar output | the goal is disclosure completeness, not a universal safety score | mark missing source, ambiguous code and unsafe retry as separate blanks | whether future docs revise the label or behavior |
来源地图
- Bybit API Documentation:Error Codes(bybit-v5-error)
- Bybit API Documentation:Rate Limit Rules(bybit-v5-rate-limit)
- Coinbase Developer Documentation:List Accounts(coinbase-list-accounts)
- Coinbase Developer Documentation:Advanced Trade WebSockets(coinbase-ws-auth)
- OKX API Documentation:OKX API Guide(okx-api-docs)
控制说明
1. Error taxonomy
这一项要求读者把公开来源翻译成操作规则。这里的含义是:a code is useful only when mapped to documented meaning。可执行动作是:record public source, exact code label and endpoint class。仍然未知的是:whether the same code has product-specific meanings。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、安全保证、恢复保证、平台排名或价格暗示。
2. Retry class
这里的含义是:rate-limit and permission failures require different recovery paths。可执行动作是:separate backoff, credential review, permission review and hard stop cases。仍然未知的是:whether the original request already changed account state。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
3. Permission scope
这里的含义是:private endpoints can fail because the key, account or product scope is wrong。可执行动作是:map key permission and account surface before retrying。仍然未知的是:whether support-side status changes the diagnosis。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
4. Non-secret evidence
这里的含义是:incident records must not leak credentials or account balances。可执行动作是:store endpoint name, non-secret code, timestamp, source URL and stop rule。仍然未知的是:whether a screenshot contains private account data。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
5. Radar output
这里的含义是:the goal is disclosure completeness, not a universal safety score。可执行动作是:mark missing source, ambiguous code and unsafe retry as separate blanks。仍然未知的是:whether future docs revise the label or behavior。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
仍需明确的未知项
- whether the same code has product-specific meanings
- whether the original request already changed account state
- whether support-side status changes the diagnosis
- whether a screenshot contains private account data
- whether future docs revise the label or behavior
实用结论
NexuAlpha Radar 只在 error code 能映射到公开来源且不暴露凭据时,把 private API error code 视为 disclosure evidence。Bybit 文档提供 permission、expiry 与 rate-limit labels;Coinbase 文档提供 authenticated account 与 WebSocket surfaces;OKX API 文档披露 WebSocket login 与 subscription controls。有效 radar output 不是平台排名,而是核验操作者能否在 private connector 继续前记录 non-secret endpoint、source URL、error label、retry class、permission scope 与 stop condition。 本文停在证据边界内,帮助读者决定下一步核验什么,而不是把公开文档改写成私人账户、钱包、API key、池子路径、稳定币余额、代币化资产或政策框架在任何未来条件下都能成功的承诺。
相關專題與工具:交易所 API 與行情資料核查
來源與證據
05- Error Codes
- Rate Limit Rules
- List Accounts
- Advanced Trade WebSockets
- OKX API Guide · okx.com