Recherche vérifiée par sources: Coinbase Kraken OKX Websocket

Decision Matrix

Source Map

• Coinbase Developer Documentation: Exchange WebSocket Channels (coinbase-websocket-channels)
• Kraken Developers: WebSocket v2 Add Order (kraken-ws-add-order)
• Kraken Developers: WebSocket v2 Cancel Order (kraken-ws-cancel-order)
• OKX Technical Support: OKX API guide WebSocket order channel (okx-order-channel)

Control Notes

1. Authentication scope

Authentication scope is the decision point where public documentation must become an operating rule. In this package, it means private order streams and trading methods require permissions that differ by venue. The practical action is to record the exact key scope before subscribing or cancelling. The unresolved edge is private account permission changes after the key was created, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

2. Subscription channel

Subscription channel is the decision point where public documentation must become an operating rule. In this package, it means each venue names channels and methods differently. The practical action is to map every message to its official source before normalizing events. The unresolved edge is temporary channel deprecations or beta-only fields, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

3. Client identifier

Client identifier is the decision point where public documentation must become an operating rule. In this package, it means client order identifiers help join local intent to venue state. The practical action is to store a non-secret client id and venue order id pair. The unresolved edge is duplicate IDs generated by a faulty bot, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

4. Cancel acknowledgement

Cancel acknowledgement is the decision point where public documentation must become an operating rule. In this package, it means a cancel request or acknowledgement is not always the same as final cancelled state. The practical action is to wait for venue state or REST backfill before freeing risk limits. The unresolved edge is race conditions with fills during cancellation, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

5. Reconnect gap

Reconnect gap is the decision point where public documentation must become an operating rule. In this package, it means WebSocket drops can hide lifecycle transitions. The practical action is to backfill from REST or account history after reconnect. The unresolved edge is whether all interim transitions are recoverable from public APIs, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

6. Evidence hygiene

Evidence hygiene is the decision point where public documentation must become an operating rule. In this package, it means logs should contain endpoint, timestamp, client id and state label without secrets. The practical action is to redact API keys, signatures and private balances. The unresolved edge is internal retention policy for trading logs, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

7. Stop rule

Stop rule is the decision point where public documentation must become an operating rule. In this package, it means new orders should pause when cancel state cannot be reconciled. The practical action is to freeze automation until local and venue states agree. The unresolved edge is manual override and incident commander authority, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

Known Unknowns

• private account permission changes after the key was created
• temporary channel deprecations or beta-only fields
• duplicate IDs generated by a faulty bot
• race conditions with fills during cancellation
• whether all interim transitions are recoverable from public APIs
• internal retention policy for trading logs
• manual override and incident commander authority

Practical Takeaway

Coinbase, Kraken and OKX expose different WebSocket surfaces for order lifecycle monitoring, so a cancel-state runbook should not normalize every message into one generic event. Coinbase documents Exchange WebSocket channels, Kraken documents WebSocket v2 add_order and cancel_order methods, and OKX documents an order channel under its trading WebSocket API. The decision outcome is to reconcile authentication scope, subscription channel, client order identifier, cancel acknowledgement, final order status and REST backfill before treating a local bot state as final. The article stops at the evidence boundary. It helps the reader decide what to inspect next without converting public documentation into a promise that a private account, wallet, callback, policy framework, settlement route or liquidity position will work under every future condition.