Recent payouts

get

https://api.avvio.xyz/business/api/v1/payments/organizations/{orgId}/orders

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

orgId

string

required

length ≥ 1

The opaque organization id issued to you, normally CUID-shaped (for
example cmsx…). It is not an org_-prefixed alias. Pass it unchanged
in every organization-scoped path.

Query Params

updatedSince

date-time

The change feed. Return payouts whose state changed at or after
this time, oldest-changed first.

Ordinary listing is newest-first by CREATION, which by construction
can never tell you that an OLD payout changed — and completed → failed on a bank return, days later, is exactly the change a ledger
cannot afford to miss. Page forward with nextCursor, carry the last
updatedAt you saw as your watermark, and you will observe every
revision without re-reading your whole history.

AT-LEAST-ONCE, not exactly-once: updatedSince is inclusive, so
resuming from your watermark re-reads the row at that instant.
Dedupe on payoutId + updatedAt.

status

array of objects, unique

length ≥ 1

One comma-separated list of canonical statuses, e.g. processing,completed.

endUserId

string

Your id for the person the payout belongs to.

reference

string

Your payment reference, matched exactly.

createdAfter

date-time

createdBefore

date-time

limit

integer

1 to 100

Defaults to 50

cursor

string

The nextCursor from the previous page, passed back verbatim. It
is opaque — do not parse or construct one.

Responses

200A page of payouts. Newest-created first, or oldest-CHANGED first when updatedSince is set.

401Missing, invalid, or revoked key — or a key on a route that does not accept one.

403Valid key, wrong organization.