Search payable rows

Query the payer-seat billing-document search rows ("what I owe") — the mirror of /search/invoice-rows, recreating legacy /search/invoice-row as seen from the client seat. Identical execution model: every filter runs inside the Atlas $search pipeline; relevance sort when filter[searchString][eq] is present; otherwise default sort is dueDate descending. Rows include documents the Payable resource does not serve: payroll batch invoices (metadata.invoiceType = approvedInvoicesPayment, served on V3 as a PayrollRun) and personal-paylink invoices (metadata.creationSource = personalPaylink). Both are excluded from /v3/payments/payables list results and 404 on a per-id read, so a surface mirroring the payables list should exclude them here too — filter[metadata.invoiceType][ne]=approvedInvoicesPayment and filter[metadata.creationSource][ne]=personalPaylink, the legacy /search/invoice-row base filter. Account scope is enforced server-side (no filter[accountIds] — target a child account via X-Wingspan-Account).

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
page
object

Pagination query parameters. Serializes as page[size], page[token], page[mode], and page[resultSetId].

sort
object

QueryQL sort namespace for billing-document rows, sort[field]=asc|desc — exactly one field. createdAt/updatedAt/openedAt/paidAt address the row's events.* timestamps; dueDate, amount, and scheduledPaymentDate address row fields (scheduledPaymentDate is the legacy internal.events.paymentDueAt sort key). When filter[searchString][eq] is present, relevance (searchScore descending) is the primary sort and the requested field becomes the secondary sort. Default when omitted: dueDate descending (the legacy /search/invoice-row default).

filter
object

QueryQL filter namespace; same serialization and operator rules as /search/invoice-rows. x-legacy-filter names the legacy /search/invoice-row filter each field replaces (client-seat view). Dynamic paths (filter[metadata.<key>][eq]) are accepted in addition to the named fields.

Headers
string
^(?:[A-Za-z0-9_.]{22}|[a-f0-9]{24})$

Select the Account for an Account-scoped operation. A direct ServiceAccount API key MUST supply this header, and the target must be within the ServiceAccount owner's or Authorization grant's Account boundary. A Person bearer may select an Account on which it has an active Stakeholder, and an Account session may select its bound Account (or a descendant only when the session explicitly includes descendants).

string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json