SaaSFlow
DevelopersAPIReferencetransactions

Uncategorize

Strip the categorizations from a selection of transactions, leaving the transactions themselves untouched. Use it to undo a bad bulk categorization or a wrong vendor default before re-running it. The rows go back to open and disappear from the P&L until they are categorized again. Same `selection` shape and 10,000-row cap as the other bulk endpoints.

Authentication

You're not signed in. Either sign in at app.saasflow.com and reload (then pick sessionCookie), or paste a SaaSFlow sf_… API key in the bearerAuth field below.
POST
/companies/{companyId}/transactions/uncategorize

Authorization

Authorization<token>

A SaaSFlow API key (format sf_…) or an OAuth bearer token. Paste only the key — the proxy adds the Bearer prefix. Create an API key in Settings → Company settings → API keys — see API keys.

In: header

Path Parameters

companyId*string
Length1 <= length

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

curl -X POST "https://example.com/companies/string/transactions/uncategorize" \  -H "Content-Type: application/json" \  -d '{    "selection": {      "mode": "ids",      "ids": [        "string"      ]    }  }'
{  "success": true,  "affected": 0}

Batch delete

Delete many transactions at once. `selection` takes either `mode: "ids"` with an explicit list, or `mode: "filter"` with the same filters `POST /transactions/search` accepts plus `excludedIds` for rows the user unticked, which is how "select all matching" works without sending every id. Selections over 10,000 rows are refused with 413. A selection containing integration-managed transactions is refused with 422 rather than partially applied.

Batch edit

Apply one patch to a whole selection of transactions: reassign them, set notes, or push a categorization template across all of them. Fields left out of `patch` are untouched, and null clears a field. The categorization template deliberately has no transfer target, because counter transactions are booked from the vendor's stored default rather than from anything passed here. Same `selection` shape and 10,000-row cap as the other bulk endpoints.