Skip to main content
A network error halfway through a write leaves you not knowing whether it landed. Send an Idempotency-Key header and you can simply send the same request again: the second attempt returns the first answer instead of doing the work twice.
Generate a fresh key (a UUID works well) for each distinct write, and reuse it only when retrying that same write. There are two implementations, one for each surface. They share the header name and the 24-hour lifetime, and differ in where keys are stored.

REST API (/api/...)

Whatever the first response was is what gets replayed, including an error. If a request failed because of something you then fixed, send the corrected request with a new key.
On the REST API the key store is held in memory by the server instance that answered. It is lost on a restart or deploy and is not shared between instances, so a retry that reaches a different instance runs again. Treat it as protection against quick client retries, not as a durable guarantee. For a create that must never duplicate, POST /api/bank/transactions also accepts a clientRequestId field (8–64 letters, digits or dashes) that is stored with the transaction itself: sending it again returns the saved row with replayed: true.
A few routes do not go through the REST store: the chat routes (/api/chat/...), receipt analysis and commit (/api/receipts/...), and the MCP endpoint (/mcp, which is outside /api). The API reference lists the Idempotency-Key parameter on every operation where it applies.

Integration API (/api/integrations/v1)

The Integration API keeps its keys in the database, so they survive restarts and are shared by every instance. Statement imports are idempotent in two more ways: the same file sent again is recognised by its contents and not imported twice, and entries already stored are skipped by their own ids.

Undo is separate

Idempotency stops a retry from doubling a write. To reverse a batch edit after it happened, see the data history endpoints (GET /api/data-history, then GET /api/data-history/change-sets/{id} to preview and POST /api/data-history/change-sets/{id}/undo to undo), which work for 30 days after the batch.