Everything that has happened to your payouts, in order

The reconciliation primitive. Each event is written once and never
changes, carries its own id, and sequence is a total order you cursor
on — so "page forward from where I left off" is expressible, which
listing payouts cannot do: that is ordered by CREATION and can never
surface a change to one you have already read.

payout.returned is its own type rather than a flavour of
payout.failed, because a bank returning a settled payment days later is
the one event that reverses something you already booked.

At-least-once — dedupe on id. And the cursor is sequence, not a
timestamp: timestamps tie, and a tie is indistinguishable from a
boundary.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
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
string
^\d+$

Return events after this sequence. Use nextSince.

string
length ≥ 1

Everything that ever happened to one payout.

integer
1 to 500
Defaults to 100
Responses

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