---
title: "Delete Bexio Account"
method: DELETE
path: "/bexio-accounts/{account_id}"
tags: ["integrations"]
---

# Delete Bexio Account

`DELETE /bexio-accounts/{account_id}`

## Request

- Base URL: `https://app.zeno-works.ch` (the document declares no server; this is the origin it was published from)
- URL: `https://app.zeno-works.ch/bexio-accounts/{account_id}`
- Auth: none declared

Delete one bexio integration account from a company (accountant/owner).

Drops the credentials and the sync link. Documents already imported stay — booked ones
included — and only lose their link to the account.

**A later reconnect re-walks the whole backlog.** The row being deleted IS the sync
cursor (``last_seen_updated_at`` / ``last_seen_id`` / ``backfill_floor``), so a fresh
account starts from the floor exactly as ``reset_bexio_cursor`` does — burning API
quota, tripping rate-limit throttling, and re-ingesting invoices the tenant may since
have removed — and every invoice the old account already imported, a second time next to
the kept one, since the dedup key includes the account. Delete-then-reconnect is
therefore not a cheap round trip; prefer fixing the existing account. (An earlier
version of this docstring claimed the opposite, and FastMCP serves it verbatim as the
tool description an agent acts on.)

## Path parameters

- `account_id` string, required

## Headers

- `authorization` string, nullable

## Cookies

- `access_token` string, nullable

## Response `200`

Successful Response

- MsgResponse: The ``{"msg": "..."}`` envelope — the error contract and many successes.
  - `msg` string, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/zeno-works/apis/zeno-api.md) · [All operations](https://skmtc.dev/zeno-works/apis/zeno-api/llms.txt) · [OpenAPI document](https://skmtc.dev/zeno-works/apis/zeno-api/revisions/1eb93dde146c?raw)