List Reserve Updates
Returns an event’s reserve-update feed: user expected-total updates and
the automatic rows for reserve-eroding payments of currently-linked live
invoices, discriminated by kind. A reserve history reset establishes a
per-category horizon — rows at or before it never render, and the reset
itself renders as one marker row.
Rows are ordered by journal execution order, newest first. An event with
no reserve history — unknown ids included — reads as an empty feed.
categoryId narrows the feed to one reserved category.
Required permission: company.payment:read
Authorizations
API key authentication. Send your raw API key as the Authorization header value with NO scheme prefix — Authorization: YOUR-API-KEY. Do NOT prefix it with Bearer or ApiKey, and do not use an X-API-Key header; those are not accepted.
Path Parameters
Company identifier
Event identifier
Query Parameters
Only feed rows for this reserved category
Response
The event's reserve-update feed, newest first
A reserve-update feed row, discriminated by kind: user (a set of the expected total), erodingPayment (an automatic row for a reserve-eroding payment), or reset (the history-reset marker).
- Option 1
- Option 2
- Option 3
