Reorder
Set the display order of categories. Each id's `order` becomes its position in the array you send, so send the full list rather than the few you moved.
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 <= lengthRequest Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
curl -X PUT "https://example.com/companies/string/categories/reorder" \ -H "Content-Type: application/json" \ -d '{ "categoryIds": [ "string" ] }'{ "success": true}Merge
Merge several categories into one, in a single transaction. Creates the category described by `newCategory`, then repoints everything that referenced the old ids: transaction categorizations, the default categorization on customers and vendors, and the default category on accounts. The old categories are deleted afterwards. This is how to retire duplicates without stranding history, since a plain delete is refused while transactions still use the category. One thing to know before running it: plan items on the old categories are deleted rather than repointed, so a merge drops that part of the financial plan. Returns the new category.
List customers
List customers, sorted by name, each enriched with its transaction count, subscription count, and current committed MRR. The response shape depends on `limit`: send it and you get `{ items, totalCount }`, omit it and you get a bare array of every customer. `q` matches on name, and `onlyActive=true` keeps just the customers whose current cMRR is above zero. The enrichment fields are gated separately from customer master data, so a caller without `transactions:read` or `subscriptions:read` gets those keys omitted rather than nulled.