Search invoice rows

Query the payee-seat billing-document search rows ("invoices I issued") — the V3 recreation of legacy /search/invoice-row for the member seat. Identical execution model to /search/payee-rows: every filter — equality included — runs inside the Atlas $search pipeline against the materialized row collection; this endpoint never touches the operational database. When filter[searchString][eq] is present, results are relevance-ranked (searchScore descending) with any explicit sort[field] applied as the secondary sort; when absent, default sort is dueDate descending (the legacy default). Rows include the synthetic payment records legacy callers hid from invoice lists (metadata.invoiceType = approvedInvoicesPayment) — exclude them with filter[metadata.invoiceType][ne], or select them with [eq] to list payroll aggregate documents. Account scope is enforced server-side as non-negotiable filter clauses; there is 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. Serialize as filter[field][operator]=value; for array operators use filter[field][anyOf][]=value. x-legacy-filter names the legacy /search/invoice-row filter each field replaces. 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