Transfer chain
Resolve the full path of a linked transfer, ordered from source to destination. Money moving between two accounts is two transactions, and when the legs cannot be matched directly SaaSFlow routes them through a transit account, which puts extra hops in between. This returns every node on that path so the whole movement can be shown as one thing. `nodes` is empty when the categorization is not a linked transfer.
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 <= lengthQuery Parameters
The transfer categorization whose chain to resolve.
1 <= lengthResponse Body
application/json
curl -X GET "https://example.com/companies/string/transactions/string/transfer_chain?categorizationId=string"{ "nodes": [ { "transactionId": "string", "categorizationId": "string", "accountId": "string", "accountName": "string", "isTransit": true, "amountValue": "string", "amountCurrency": "string", "date": "string", "isCurrent": true } ]}Link stripe invoices
Book one or more Stripe invoices onto the transaction that paid them, taking the service period, tax split and customer from each invoice instead of the payment date. Pass several ids when one transfer settled several invoices. Re-linking an invoice replaces only the categorizations it produced, so anything categorized by hand is kept. If the payer settled for a different amount than was invoiced, the difference is left uncategorized and the transaction stays open, because only the customer knows what the difference was.
Retrieve transaction
Retrieve one transaction with everything hanging off it: its account, categorizations, comments, and attached files. This is the detail view, so it returns considerably more than the same row does in a list. Returns 404 if the transaction does not exist or belongs to another company.