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.
Authentication
sf_… API key in the bearerAuth field below.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
1 <= length1 <= lengthResponse Body
application/json
curl -X GET "https://example.com/companies/string/vendors/string/apply-default-categorization/preview"{ "empty": 0, "autoAssigned": 0, "userEdited": 0}Update vendor
Update a vendor. Only the fields you send change. A new `defaultCategorization` applies to future matches only; to push it onto transactions already booked against this vendor, call `apply-default-categorization` afterwards.
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.