Quellengeprüfte Recherche: Kraken Websocket V2 ADD

Decision Matrix

Source Map

• Kraken API Center: Spot WebSocket v2 Documentation (kraken-ws-v2)
• Kraken API Center: Add Order (kraken-add-order)
• Kraken API Center: Cancel Order (kraken-cancel-order)
• Kraken API Center: Get Websockets Token (kraken-ws-token)

Control Notes

1. Authentication state

Authentication state is the point where public documentation must become an operating rule. In this package, it means private order channels depend on token or authenticated session state. The practical action is to record token source and refresh rule without storing secrets. The unresolved edge is token expiry, revocation, private account status and future authentication changes, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

2. Order identifier

Order identifier is the point where public documentation must become an operating rule. In this package, it means client and exchange identifiers serve different reconciliation jobs. The practical action is to log non-secret identifiers and pair them with command timestamps. The unresolved edge is identifier collision, delayed acknowledgement and private-account filters, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

3. Acknowledgement

Acknowledgement is the point where public documentation must become an operating rule. In this package, it means command acceptance is not identical to final execution or cancellation. The practical action is to capture acknowledgement and final order-state evidence separately. The unresolved edge is partial fills, race conditions and stale client state, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

4. Backfill

Backfill is the point where public documentation must become an operating rule. In this package, it means WebSocket state may need REST or private-channel reconciliation after reconnect. The practical action is to write a backfill rule before using the stream for automation. The unresolved edge is whether every lost event is recoverable from public or private endpoints, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

5. Stop condition

Stop condition is the point where public documentation must become an operating rule. In this package, it means automation should stop if token state, acknowledgement or final state is missing. The practical action is to pause live order logic until lifecycle evidence is complete. The unresolved edge is future venue behavior and support-side order reconstruction, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

Known Unknowns

• token expiry, revocation, private account status and future authentication changes
• identifier collision, delayed acknowledgement and private-account filters
• partial fills, race conditions and stale client state
• whether every lost event is recoverable from public or private endpoints
• future venue behavior and support-side order reconstruction

Practical Takeaway

Kraken WebSocket v2 order controls should be treated as a lifecycle with command, acknowledgement, execution and reconciliation states. Kraken documents add_order, cancel_order and private execution surfaces for the Spot WebSocket v2 API. The practical outcome is to record authentication, client order identifier policy, acknowledgement evidence, execution-report backfill, cancel outcome and manual pause conditions before relying on a WebSocket session for live order control. 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, API key, pool route, stablecoin balance, tokenized asset or policy framework will work under every future condition.