Date and time - Documentation

All dates and times the API accepts and returns are in Coordinated Universal Time (UTC) and follow ISO 8601, a standard that is both human-readable and machine-parsable. Timestamps carry a time component; some fields are calendar dates without one.

Timestamps

Timestamps follow the pattern YYYY-MM-DDTHH:mm:ss.ffffffZ:

Part	Meaning
`YYYY`	4-digit year
`MM`	2-digit month (01-12)
`DD`	2-digit day of the month (01-31)
`T`	Separator between the date and time components
`HH`	2-digit hour (00-23)
`mm`	2-digit minute (00-59)
`ss`	2-digit second (00-59)
`ffffff`	Fraction of a second, returned with microsecond precision and optional in what you send
`Z`	The date and time are in UTC

For example, inserted_at and updated_at come back as 2026-10-07T20:16:02.471297Z: October 7, 2026 at 20:16:02.471297 UTC. Query filters such as from_datetime and to_datetime take the same format, for instance 2026-10-01T00:00:00Z.

Dates without time

Some fields are calendar dates with no time component and follow the pattern YYYY-MM-DD, for example 2026-10-25. They are the business dates of a receivable or a payment:

the due_date of a boleto or of the first payment of a recurrence;
the start_date and end_date of a recurrence;
the expiration_date and issue_date of a boleto;
the date of each discount in due_detail.discount.fixed_until_due.amounts.