List scheduled Pix payments
Returns a page of the organization’s scheduled payments, newest settlement date first. Paging is by opaque cursor rather than offset: a schedule registered between two pages would shift every later row under an offset and silently skip one. Echo the cursor verbatim. The page carries no attempt history — that is per-schedule data a list view does not show, and it is on the single-schedule route instead. Filtering by recurrence_id is how the occurrences of a recurring series are enumerated: an occurrence IS a scheduled payment, so it is listed here rather than under a route of its own, which would give the same row two identities.
Authorizations
JWT bearer token issued by the identity provider.
Query Parameters
Page size, 1..100. Absent or 0 means 20. A negative value or one above 100 is REFUSED, never clamped -- a clamped page size makes a caller believe it read everything.
0 <= x <= 10020
Opaque cursor from a previous page's pagination block. Echo it verbatim -- it is not a document to build.
Narrow to one payer account.
Narrow to one lifecycle status.
PENDING, EXECUTING, DISPATCHED_OUTCOME_UNKNOWN, AWAITING_RETRY, SETTLED, CANCELLED, FAILED Earliest settlement date to include, inclusive.
"2026-09-01"
Latest settlement date to include, inclusive.
"2026-09-30"
Narrow to the occurrences of ONE recurring series. This is how a series' occurrences are enumerated: an occurrence IS a scheduled payment, so it is listed here rather than under a route of its own, which would give the same row two identities.
"019606a1-3b4c-7d8e-9f01-234567890abc"

