HTTP status: 409 · Title: “Confirmation expired”Documentation Index
Fetch the complete documentation index at: https://docs.kash.bot/llms.txt
Use this file to discover all available pages before exploring further.
When it fires
The confirmation token is past itsconfirmation_expires_at. High-value trades have a short confirmation window (60 seconds by default; configurable per-tier).
Why it happens
- A human-in-the-loop confirmation flow took longer than the window allows.
- A queue/worker latency between
POST /v1/tradesreturning the token and the consumer calling confirm.
How to fix
- Tighten the consumer’s confirm call — ideally fire it immediately after receiving the token.
- For human-in-the-loop flows that need longer, request a per-key window extension (mm tier customers who pipeline trades through human review get longer windows).
- The trade is automatically cancelled when the window expires — re-create it to retry.