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.
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.
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.