Coinbase Advanced Trade WebSocket 账户通道清单
本文正文暫以英文原文展示，翻譯版本需完成來源複核後再發布。
已验证事实边界
1. Coinbase Advanced Trade WebSocket documentation describes setup, authentication and subscription workflows for Advanced Trade WebSockets. 2. Coinbase List Accounts API reference documents an authenticated endpoint for retrieving account information. 3. Coinbase Advanced Trade Portfolios documentation says portfolios can segregate strategies and that API keys can be scoped to portfolio resources. 4. Coinbase Create Portfolio API reference documents a portfolio endpoint requiring authorization. 5. Together, these sources support a checklist for account-channel scope, authorization and reconciliation rather than a blanket claim that every key can access every account. 6. These sources do not prove a private account can create portfolios, trade every product, avoid compliance review, bypass region rules or recover from an integration failure.
收起完整分析
决策矩阵
文章表格：可橫向滑動，或聚焦表格區域後使用方向鍵。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Channel purpose | market data, account data and order workflows have different risk | name the channel purpose before subscribing or storing messages | whether a channel emits account-specific data under every portfolio state |
| Portfolio scope | portfolio boundaries can segment strategies and API-key resource access | map key, portfolio, account and strategy owner before production use | whether a portfolio deletion or scope change leaves stale automation |
| Authorization path | private endpoints require bearer-token or key-based authorization | document token generation method without storing secrets in reports | whether a token library upgrade changes the signed URI or header behavior |
| Reconnect plan | private sockets need recovery rules after disconnects | define replay, resubscribe, sequence check and authoritative REST reconciliation | whether messages were missed while the socket was down |
| Evidence stop rule | a passing local socket test is not a production permission claim | record source URL, access time, channel, non-secret error and stop condition | whether private account controls narrow or expand what the public docs imply |
来源地图
- Coinbase Developer Documentation：Advanced Trade WebSockets（coinbase-ws-auth）
- Coinbase Developer Documentation：List Accounts（coinbase-list-accounts）
- Coinbase Developer Documentation：Advanced Trade Portfolios（coinbase-portfolios）
- Coinbase Developer Documentation：Create Portfolio（coinbase-create-portfolio）
控制说明
1. Channel purpose
这一项要求读者把公开来源翻译成操作规则。这里的含义是：market data, account data and order workflows have different risk。可执行动作是：name the channel purpose before subscribing or storing messages。仍然未知的是：whether a channel emits account-specific data under every portfolio state。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、安全保证、恢复保证、平台排名或价格暗示。
2. Portfolio scope
这里的含义是：portfolio boundaries can segment strategies and API-key resource access。可执行动作是：map key, portfolio, account and strategy owner before production use。仍然未知的是：whether a portfolio deletion or scope change leaves stale automation。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
3. Authorization path
这里的含义是：private endpoints require bearer-token or key-based authorization。可执行动作是：document token generation method without storing secrets in reports。仍然未知的是：whether a token library upgrade changes the signed URI or header behavior。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
4. Reconnect plan
这里的含义是：private sockets need recovery rules after disconnects。可执行动作是：define replay, resubscribe, sequence check and authoritative REST reconciliation。仍然未知的是：whether messages were missed while the socket was down。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
5. Evidence stop rule
这里的含义是：a passing local socket test is not a production permission claim。可执行动作是：record source URL, access time, channel, non-secret error and stop condition。仍然未知的是：whether private account controls narrow or expand what the public docs imply。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
仍需明确的未知项
- whether a channel emits account-specific data under every portfolio state
- whether a portfolio deletion or scope change leaves stale automation
- whether a token library upgrade changes the signed URI or header behavior
- whether messages were missed while the socket was down
- whether private account controls narrow or expand what the public docs imply
实用结论
Coinbase Advanced Trade WebSocket 工作应被视为 account-channel change control，而不是简单 market-data socket。Coinbase 文档描述 Advanced Trade WebSocket setup、authentication 和 subscriptions，账户列表 endpoint，以及 API key 可按 portfolio scope 管理的 portfolio behavior。实际更新是：在 account data 或 order workflow code 推进前，记录 channel purpose、portfolio scope、bearer-token generation path、read-versus-trade need、reconnect plan、message reconciliation 与 non-secret evidence。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、API key、池子路径、稳定币余额、代币化资产或政策框架在任何未来条件下都能成功的承诺。
相關專題與工具:交易所 API 與行情資料核查