---
title: "Remove Account"
method: POST
path: "/api/openbanking/remove-account/{connection_id}"
tags: ["openbanking"]
---

# Remove Account

`POST /api/openbanking/remove-account/{connection_id}`

## Request

- Base URL: `https://api.earmarkiq.app` (the document declares no server; this is the origin it was published from)
- URL: `https://api.earmarkiq.app/api/openbanking/remove-account/{connection_id}`
- Auth: HTTP bearer

Remove ONE account at a bank without disconnecting the bank.

Parks the connection as status "removed" (the pot pattern): no future
syncs, hidden from every surface, transactions retained but hidden.
The Finexer consent is NOT touched — sibling accounts on the same
consent keep syncing, and the account can be restored without a new
bank authorisation.

If this is the LAST account at the bank, the consent is deliberately
left live and idle rather than revoked: revoking it would make the
promised no-re-auth restore impossible, and ending the bank's access
is exactly what the separate "Disconnect this bank" action is for.
The consent still expires on its own 90-day clock if never used.

## Path parameters

- `connection_id` string, uuid, required

## Response `200`

Successful Response

- RemoveAccountResponse
  - `connection_id` string, required
  - `status` string, required
  - `removed_at` string, required
  - `transactions_preserved` boolean, required
  - `consent_still_active` boolean, required
  - `remaining_accounts_at_bank` integer, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/earmarkiq/apis/earmark-api.md) · [All operations](https://skmtc.dev/earmarkiq/apis/earmark-api/llms.txt) · [OpenAPI document](https://skmtc.dev/earmarkiq/apis/earmark-api/revisions/4a2c41907105?raw)