Deletes a bank account, keeping it recoverable.

DELETE /banking/bank-accounts/{id}

Group: Banking › Bank Accounts · Operation ID: deleteBankAccount

The response is empty. This is a recoverable soft delete. The account is flagged deleted, unlinked from its chart of accounts, and, for an integration account that has a fingerprint, added to the recovery list behind "Recover Accounts". It disappears from the get, list and search endpoints at once, because those return only accounts that are not deleted. Two accounts get no recovery row and cannot be restored this way: a manual account, and any account without a fingerprint.

This is not the counterpart of DELETE banking/bank-transactions/:id, which is an irreversible hard delete.

Unmatched and suggested transactions on the account are hard-deleted as part of the removal, and for a SaltEdge account the bank consent is revoked. An account that has a matched or auto-matched transaction is refused with BANK_ACCOUNT_IN_USE. The underlying action can override that case, and it is deliberately not published, so this endpoint cannot force it through.

Open in the interactive reference

Parameters

Name	In	Type	Required	Description
`Api-Version`	header	`"v1"`	yes	The API version this request targets, named by its public identifier. Required on every request; omitting it, or naming a version this company does not have, is answered with 400. This document describes version `v1`.
`Idempotency-Key`	header	string	no	An opaque caller-chosen string (1-255 characters) that makes this request safe to retry. Repeating the same key with an identical request body replays the original response instead of re-executing - but only once that original request succeeded; a failed attempt re-executes on retry. Repeating the key with a different body is answered with 422. A key still in flight is answered with 409 - as is a key whose original request was interrupted before it finished, for a few minutes afterwards, until that attempt is presumed dead. A completed response stays replayable for 24 hours. The key is scoped to the caller, not to the action: reusing it for a different action is answered with 409 or 422 rather than treated independently. On read actions this header is ignored. On write actions that cannot offer the guarantee it is answered with `400 IDEMPOTENCY_NOT_SUPPORTED` rather than silently ignored.
`id`	path	string	yes	The unique identifier for the bank account to delete.

Response

200 Success

Response headers

Idempotency-Replayed — Present and true only when this response replays a previously stored one for the same Idempotency-Key, rather than reflecting a live execution. Absent on a live response - never sent as false.

Errors

Code	Status
`NOT_FOUND`	400
`BANK_ACCOUNT_IN_USE`	400
`REMOVAL_FAILED`	400
`IDEMPOTENCY_KEY_CONFLICT`	409
`IDEMPOTENCY_PAYLOAD_MISMATCH`	422

Statuses

400 — Invalid request or business failure. Codes: NOT_FOUND, BANK_ACCOUNT_IN_USE, REMOVAL_FAILED
401 — Missing or invalid access token
403 — Not authorized
404 — Not found
409 — The Idempotency-Key is still being processed by another request.
422 — The Idempotency-Key was already used with a different request payload.
429 — Too many requests
500 — Internal server error