created_at field in GET /v2/document-management/documents will return UTC
Announced: 24.06.2026
Effective date: 06.07.2026
Affected endpoint: GET /v2/document-management/documents the created_at field in the document list response will change its value:
Before:
- Format: Datetime:
2023-11-17 11:00:00 - Value: Creation time in the company's configured timezone
After:
- Format: Datetime:
2023-11-17 09:00:00 - Value: Creation time in UTC
What you need to do
If your integration displays created_at to users in their local timezone, convert from UTC in your application — the value is now always UTC, independent of the company's timezone setting.
Gradual rollout
This will be rolled out in phases over 6–7 weeks. For documents created before this change, the UTC value is derived by reading the raw stored value and treating it as UTC — it will not reflect a true timezone conversion. If your company's timezone is not UTC, these historical timestamps may be off by the UTC offset. For example, a document originally recorded at 11:00 AM in a UTC+2 timezone will appear as 2023-11-17 11:00:00 rather than the accurate 2023-11-17 09:00:00.