Dates & timezones

Format

All timestamps are ISO 8601 / RFC 3339. Two forms are accepted on input:

Form	Interpretation
2026-05-01T14:30:00Z	UTC
2026-05-01T14:30:00+03:00	Local with explicit offset
2026-05-01	Date only — stored as midnight UTC

Outputs are always returned as UTC, e.g. 2026-05-01T14:30:00Z.

Recommendation

Send timestamps with an explicit offset. Naive strings like 2026-05-01T14:30:00 (no Z, no offset) will be rejected with validation_error.

Fields that use timestamps

Resource	Field
Orders	order_date, due_date, created_at
Records	created_at, updated_at

Common mistakes

• Local time without offset. Date strings like 2026-05-01 14:30:00 are not valid.
• Epoch seconds or millis. Not accepted on any endpoint. Convert at the edge.
• Mixed timezone policy. If your ERP emits timestamps in local time without offset, configure your ETL to convert to UTC before sending.