Twitter API v2 created_at display zone configuration

Twitter API v2 returns created_at for tweets and users in ISO 8601 UTC with a trailing Z. The API does not expose a server-side parameter to request a regional time zone conversion.

Localization to a viewer’s device zone, an author’s profile zone, or a fixed platform zone must be decided by the client or backend. The API supplies no DST-aware rendering rule, and historical timestamps crossing daylight-saving boundaries can change local offset depending on the chosen zone.

The configuration goal is to store the original instant and render it consistently across viewers while preserving chronological ordering. The target display zone and fallback behavior when profile zone information is unavailable remain unspecified.

What display zone should be used by default when author profile zone is not available? Should historical DST transitions be resolved using the viewer zone or the author zone? Is profile time zone data treated as a permission boundary for timestamp rendering?