---
title: "Delete Override"
method: DELETE
path: "/api/transactions/{transaction_id}/override"
tags: ["Transaction Overrides"]
---

# Delete Override

`DELETE /api/transactions/{transaction_id}/override`

## 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/transactions/{transaction_id}/override`
- Auth: HTTP bearer

Put the transaction back to its automatic state.

Two different things are called an "override" by the clients, and
this route undoes both (17 Oct 2026: the web's "reset category to
automatic" called it and got 404 twice):

- the TransactionOverride row (notes, excluded_from_budgets,
  is_reimbursable, reimbursed, splits) — deleted if present;
- the category the user (or their adviser) set on the row
  (`category_changed_by`), which the category endpoint writes to the
  transaction itself and, for scope "merchant", to a
  MerchantCategoryOverride rule. The rule for this merchant is deleted,
  the row is re-classified by the automatic path (the v2 category order
  for a CLASSIFY_V2 user, the rules classifier otherwise) and
  `category_changed_by` is cleared.

404 only when the transaction is not this user's. Nothing to undo is
a 200 with both flags false, so a double tap is harmless.

## Path parameters

- `transaction_id` string, uuid, required

## Response `200`

Successful Response

- OverrideDeleteResponse
  - `transaction_id` string, required
  - `override_removed` boolean, required
  - `category_reset` boolean, required
  - `merchant_rule_removed` boolean, required
  - `category` string, nullable, required
  - `category_source` string, nullable, 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)