SaaSFlow
DevelopersAPIReferencetransactions

Categorization status

Given up to 10,000 transaction ids, return which of them are still open and the amount of each. Built for review tooling that produced suggestions a while ago and needs to know what is still worth applying before showing it. "Open" is broader than uncategorized: it also covers rows whose categorizations do not sum to the amount, and incomplete transfers. `amountsById` covers every id that exists in this company, so a cluster total can be computed here rather than trusted from the caller.

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/categorization_status

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

curl -X POST "https://example.com/companies/string/transactions/categorization_status" \  -H "Content-Type: application/json" \  -d '{    "transactionIds": [      "string"    ]  }'
{  "openTransactionIds": [    "string"  ],  "amountsById": {    "property1": {      "value": 0,      "currency": "string"    },    "property2": {      "value": 0,      "currency": "string"    }  }}

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.

Import

Bulk-import transactions, which is the endpoint behind CSV upload and any backfill of history. Amounts follow the same convention as single creation: signed decimal strings, negative for money out. Transit accounts are system-managed and cannot be imported into (422). Only a count comes back, so keep your own idempotency key if the import may be retried.