SaaSFlow
DevelopersAPIReferencevendors

Apply default categorization

Re-apply a vendor's default categorization to transactions already booked against it. `applyTo` decides how far it reaches: `empty` only fills in transactions with no categorization, `autoAssigned` also overwrites what SaaSFlow categorized itself, and `all` overwrites hand-edited categorizations too. Run the `/preview` endpoint first to see the counts. If the template books a transfer, the missing counter transactions are created and counted in the response. Fails with 400 when the vendor has no default categorization to apply.

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}/vendors/{vendorId}/apply-default-categorization

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
vendorId*string
Length1 <= length

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

curl -X POST "https://example.com/companies/string/vendors/string/apply-default-categorization" \  -H "Content-Type: application/json" \  -d '{    "applyTo": "empty"  }'
{  "insertedSlices": 0,  "updatedSlices": 0,  "counterTransactionsCreated": 0}

Apply default categorization preview

Count what re-applying this vendor's default categorization would touch, without changing anything. The three buckets map onto the `applyTo` choices on the write endpoint: `empty` is transactions with no categorization yet, `autoAssigned` is ones SaaSFlow categorized itself, and `userEdited` is ones a person set by hand. Show these numbers before overwriting, since `applyTo: "all"` is what discards manual work.

Batch delete

Delete many vendors in one call. `selection` works two ways: `mode: "ids"` with an explicit list, or `mode: "filter"` with the same `q` the list endpoint takes plus `excludedIds` for the rows the user unticked. Filter mode is what "select all matching" sends, so nothing has to round-trip every id. Selections resolving to more than 10,000 vendors are refused with 413 and a body giving the count and the cap. The response reports how many rows were affected.