Skip to main content
All dates and times in the Payouts API are represented as RFC 3339 / ISO 8601 strings in UTC, with a trailing Z:
Send timestamps in the same format when a request or filter accepts one.

​
Resource timestamps

Most resources carry two standard timestamps:

​
Ordering

List endpoints always return results newest-first, ordered by createdAt descending. Ordering is fixed, there is no sortBy parameter. To narrow a list, filter it (see below) and page through with the cursor parameters described in the API reference.

​
Date-range filters

List endpoints support filtering by creation time using bracket-suffixed query parameters, which accept RFC 3339 timestamps:
The two bounds can be combined to form a closed range, and they compose with the other filters and with pagination (all filters combine with AND).

​
Timestamps in webhooks

Every webhook delivery includes an occurredAt timestamp marking when the change occurred, in the same RFC 3339 / UTC format.
Always send and interpret timestamps in UTC. If your system stores local times, convert to UTC before filtering, otherwise range boundaries will be off by your timezone offset.