بحث موثق بالمصادر: Binance Kraken OKX Cancel

Decision Matrix

Source Map

• Binance Developer Documentation: Trade - Spot WebSocket API (binance-ws-trade-cancel-all)
• Kraken API Center: Cancel on Disconnect (kraken-cancel-on-disconnect)
• OKX Technical Support: Trade REST API cancel-all-after (okx-cancel-all-after)
• Binance Developer Documentation: General REST API Information (binance-spot-rest-timing)

Control Notes

1. Action type

Action type is the decision point where public documentation must become an operating rule. In this package, it means one venue exposes an immediate cancel-all action while another documents a timer-based safety switch. The practical action is to label each control as immediate cancel, timer refresh, timer deactivate or status backfill. The unresolved edge is whether a private account has product-specific access to the endpoint, 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. Scope

Scope is the decision point where public documentation must become an operating rule. In this package, it means symbol-specific cancellation and account-wide timeout controls have different blast radii. The practical action is to record symbol, market type, account, portfolio and product family before sending a request. The unresolved edge is hidden subaccount or portfolio routing outside the local bot model, 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. Signed timing

Signed timing is the decision point where public documentation must become an operating rule. In this package, it means signed endpoints depend on timestamp, recvWindow or equivalent authentication freshness. The practical action is to sync clocks and log non-secret request ids before production use. The unresolved edge is network jitter during market stress, 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. Acknowledgement

Acknowledgement is the decision point where public documentation must become an operating rule. In this package, it means a successful request response can still precede final venue state. The practical action is to query order state after acknowledgement before releasing new risk. The unresolved edge is fills that race against the cancellation window, 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 a websocket drop can hide the transition between open, partially filled and cancelled. The practical action is to backfill from REST or account history after reconnect. The unresolved edge is whether every interim transition remains recoverable, 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 the decision record should prove control behavior without exposing credentials. The practical action is to store endpoint, time, product, symbol and state label without secrets. The unresolved edge is internal retention policy for incident 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 automation should not continue when venue and local state disagree. The practical action is to pause new orders until final order state is reconciled. The unresolved edge is who can manually override during an incident, 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

• whether a private account has product-specific access to the endpoint
• hidden subaccount or portfolio routing outside the local bot model
• network jitter during market stress
• fills that race against the cancellation window
• whether every interim transition remains recoverable
• internal retention policy for incident logs
• who can manually override during an incident

Practical Takeaway

Binance, Kraken and OKX expose different order-cancellation safety controls, so an automation runbook should separate immediate cancel-all actions from timer-based cancel-on-disconnect controls. Binance documents a Spot WebSocket API method for cancelling all open orders on one symbol, Kraken documents an authenticated cancelAllOrdersAfter WebSocket control, and OKX documents a cancel-all-after trading endpoint. The decision outcome is to define symbol scope, timeout scope, signed-request timing, acknowledgement evidence, final order-state backfill and a pause rule before treating a local bot as flat. 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.