Get how one row was booked
The exact stable journal lines behind one transactions-window row (account, name, debit, credit, VAT, dimensions, footed totals) plus its evidence documents. Document bytes are served by the existing attachment and upload endpoints; this read returns references only. The server-authored resource URI and revision own identity; row_id is display context. Omit the resource pair only for a derived payslip row.
Authorizations
Portal API key minted in portal Settings → API access. Scope read or write; pinned to one company. Send as Authorization: Bearer lac_sk_....
Query Parameters
Display context from a served row; never canonical identity.
Server-authored resource_ref.uri from the selected row. Required with resource_revision for canonical bank and journal rows; omit both only for a derived payslip row.
Server-authored resource_ref.revision from the selected row. Required with resource_uri for canonical bank and journal rows.
Response
The booking view. posted=false serves no lines, honestly.