Search payer rows

Query the payee-seat search rows ("who pays me") — the mirror of /search/payee-rows. Identical execution model: every filter runs inside the Atlas $search pipeline; relevance sort when filter[searchString][eq] is present; account scope 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, sort[field]=asc|desc — exactly one field. Sort keys address the row's events.* timestamps. When filter[searchString][eq] is present, relevance (searchScore descending) is the primary sort and the requested field becomes the secondary sort.

filter
object

QueryQL filter namespace; same serialization and operator rules as /search/payee-rows. x-legacy-filter names the legacy /search/payer-row filter each field replaces. The only dynamic path on payer rows is filter[metadata.<key>][op] (same operators and analyzed-text semantics as payee-row dynamic paths) — custom fields are payer-owned, so filter[customFields.<key>] is not available on this seat.

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