Delete a transaction
Permanently removes the transaction. This is a hard delete, the same one the web app performs — there is no soft-delete or undo, and a PSD2-connected account may re-import the movement on a later sync.
The cleanup is handled for you: payment allocations are removed with it, bank statement entries survive but lose their link, and the payment status of whatever document or expense it settled is re-derived — so deleting a matched transaction leaves its invoice correctly unpaid rather than stale.
Intended for correcting an import that landed rows it should not have — most typically a camt.053 statement uploaded for a period the account had already received over PSD2, which imports as duplicates because the parser’s duplicate check matches on the bank’s own reference and that differs between a live feed and a downloaded statement.
Requires the manage:transactions scope — a write-scoped key cannot
delete.
Authentication
JWT issued via POST /api/v1/auth/sign_in. Used by mobile and SPA clients. Revoked tokens are rejected.
Lucanto API key. Two prefixes:
lct_pat_<random><checksum>— personal access token (owner: User)lct_live_<random><checksum>— workspace token, live data
Issue keys at /settings/api_keys (personal) or
/:workspace_id/settings/api_keys (workspace). Plaintext token is
shown once and never again.
Path parameters
Transaction ID. Either the numeric id or the public_id (txn_…).
