> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/api/webhooks/financial-account-deleted.md).

# financial\_account.deleted

One of your financial accounts was deleted, on its own, by merging it into another account, or with its entity or connection.

### When it fires

The event is sent once for each account deleted, whichever way it happened:

* The account was deleted on its own, in Kick or through [Financial Accounts](https://docs.kick.co/api/api-reference/financial-accounts.md).
* The account was merged into another account. Only the account merged away sends the event; the account it was merged into stays and sends nothing.
* The account's entity was deleted. One event is sent for each of the entity's accounts.
* The account's integration connection was deleted. One event is sent for each of the connection's accounts.

A delete your own integration makes reaches your endpoint too. An account with no entity sends nothing, because the Platform API doesn't return unassigned accounts.

The event is sent after the delete is saved, to every organization with Platform API access that the account's workspace belongs to.

### Payload

```json
{
  "event": "financial_account.deleted",
  "version": 1,
  "occurredAt": 1761645600,
  "payload": {
    "financialAccountId": "3f9c2a71-5d8e-4b6a-9c1f-7e2d4a6b8c90",
    "workspaceId": "8d3a1b52-9f1d-4a7e-b0a1-2c5d6e7f8a90",
    "entityId": "b6c4d2e1-7a3f-4c8b-9e0d-1f2a3b4c5d6e"
  }
}
```

`payload` carries:

| Field                | Type | Notes                                                                                                                                                 |
| -------------------- | ---- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| `financialAccountId` | uuid | The `id` the account had on [Financial Accounts](https://docs.kick.co/api/api-reference/financial-accounts.md). Requests that use it now answer `404` |
| `workspaceId`        | uuid | Workspace the account belonged to                                                                                                                     |
| `entityId`           | uuid | Entity the account was assigned to when it was deleted                                                                                                |

The fields around it are the same on every event. See [The event envelope](https://docs.kick.co/api/webhooks.md#the-event-envelope).

### Handling it

Stop sending writes for the account and remove or archive whatever you stored for it. The event doesn't say why the account was deleted. After a merge, the merged account's transactions that weren't duplicates move to the remaining account, so expect them to show up there on your next sync.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kick.co/api/webhooks/financial-account-deleted.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
