> ## Documentation Index
> Fetch the complete documentation index at: https://developers.staging01.melio.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Timestamps

All dates and times in the Payouts API are represented as [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339) / ISO 8601 strings in **UTC**, with a trailing `Z`:

```text theme={null}
2026-07-08T15:04:05Z
```

Send timestamps in the same format when a request or filter accepts one.

## Resource timestamps

Most resources carry two standard timestamps:

| Field       | Meaning                                                                           |
| ----------- | --------------------------------------------------------------------------------- |
| `createdAt` | When the resource was created. Never changes.                                     |
| `updatedAt` | When the resource was last modified. Equal to `createdAt` until the first change. |

```json theme={null}
{
  "id": "pay_...",
  "createdAt": "2026-07-08T15:04:05Z",
  "updatedAt": "2026-07-08T15:10:00Z"
}
```

## 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:

| Filter         | Meaning                              |
| -------------- | ------------------------------------ |
| `created[gte]` | Created at or after the given time.  |
| `created[lte]` | Created at or before the given time. |

```bash theme={null}
# Payments created during the first week of July 2026 (UTC)
curl "https://api.example.com/v2/payments?created[gte]=2026-07-01T00:00:00Z&created[lte]=2026-07-08T00:00:00Z" \
  -H "Authorization: Bearer <api-key>"
```

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](/docs/webhooks) includes an `occurredAt` timestamp marking when the change occurred, in the same RFC 3339 / UTC format.

<Note>
  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.
</Note>