Search Transactions
const url = 'https://example.com/transactions?include_collapsed=false&with_category_provenance=false&limit=50&offset=0';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://example.com/transactions?include_collapsed=false&with_category_provenance=false&limit=50&offset=0'Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Fill category_source from the audit trail (register badges)
Fill category_source from the audit trail (register badges)
Responses
Section titled “Responses”Successful Response
object
Flat view: the real-account delta plus category path.
With a perspective account (the register view: GET /transactions?account=X)
the amount is that account’s signed leg; without one, transfers present
their outgoing side with a positive amount (the historical shape).
A row is a transfer only when its postings are a shape Purser creates
(DESIGN §3.3): a plain transfer, or a split loan payment — whose
category_path is the interest/fee category and remainder_amount that
posting’s amount. Any other multi-posting row is not a transfer.
A split transaction (one real leg plus several category legs, such as an
imported Quicken split; decision 87) has category_path null and
split_lines set to its category-leg count; the legs are in the detail’s
postings. Split rows are read-only.
object
True when the row is in the unreviewed set (#175): the same test as GET /transactions?reviewed=false and the review count
Category legs of a split transaction (one real leg plus two or more category legs, decision 87); 0 for every other row. Split rows are read-only.
Example
{ "items": [ { "has_linked_originals": false, "schedule_pinned": false, "split_lines": 0 } ]}Validation Error
object
object
object
Example generated
{ "detail": [ { "ctx": {}, "input": "example", "loc": [ "example" ], "msg": "example", "type": "example" } ]}