Summary
New rollout date : on & after 31st August 2026 (Based on customer feedback and impact considerations, we are extending the rollout timeline to allow customers additional time for planning, validation, and adoption activities prior to the change taking effect.)
Following the previously postponed rollout, the Public API is moving forward with an update to align time zone formatting with the modern IANA time zone identifier convention.
This change replaces the older Olson-style short format with the current IANA format to improve accuracy and reflect modern time zone standards, including changes in daylight savings observance across different regions.
For example:
- New format: America/New_York
Effective Date
Monday, June 8, 2026
Monday, August 31, 2026
Details
Date and time formatting standards are continually evolving. To provide a better user experience and maintain accuracy, we are updating our API to follow the modern IANA time zone identifier format. This standard moves away from the shorter, original time zone formats.
You can find the latest IANA tz database information here: Time Zone database
Customer Impact
Customers consuming API responses will observe a change in the format of the timeZone response fields. Time zones will now be represented by city name instead of the previous short format.
For example, EST5EDT will now appear as America/New_York in API responses.
Users who rely on the previous short format may need to adjust their applications to accommodate this change.
Impacted Resources
The following APIs will be affected by this change in the timeZone field within their responses:
/api/v2/telephony/providers/edges/timezones
/api/v2/timezones
/api/v2/gamification/contests
/api/v2/gamification/contests/{contestId}
/api/v2/gamification/scorecards/users/values/average
/api/v2/gamification/scorecards/values/trends
/api/v2/gamification/scorecards/users/{userId}/values/trends
/api/v2/gamification/scorecards/users/values/trends
/api/v2/gamification/scorecards/profiles/{profileId}/metrics/{metricId}/users/{userId}/values/trends
/api/v2/gamification/scorecards/profiles/{profileId}/metrics/{metricId}/values/trends
/api/v2/analytics/actions/aggregates/jobs
/api/v2/analytics/actions/aggregates/query
/api/v2/analytics/agentcopilots/aggregates/query
/api/v2/analytics/flows/aggregates/query
/api/v2/quality/evaluations/aggregates/query/me
/api/v2/analytics/bots/aggregates/query
/api/v2/analytics/bots/aggregates/jobs
/api/v2/analytics/conversations/aggregates/jobs
/api/v2/analytics/conversations/aggregates/query
/api/v2/analytics/flowexecutions/aggregates/query
/api/v2/analytics/flowexecutions/aggregates/jobs
/api/v2/analytics/flows/aggregates/query
/api/v2/analytics/flows/aggregates/jobs
/api/v2analytics/journeys/aggregates/query
/api/v2/analytics/journeys/aggregates/jobs
/api/v2/analytics/ratelimits/aggregates/query
/api/v2/analytics/resolutions/aggregates/query
/api/v2/analytics/resolutions/aggregates/jobs
/api/v2/analytics/summaries/aggregates/query
/api/v2/analytics/summaries/aggregates/jobs
/api/v2/analytics/surveys/aggregates/query
/api/v2/analytics/surveys/aggregates/jobs
/api/v2/analytics/taskmanagement/aggregates/jobs
/api/v2/analytics/taskmanagement/aggregates/query
/api/v2/quality/evaluations/aggregates/query/me
/api/v2/analytics/transcripts/aggregates/query
/api/v2/analytics/transcripts/aggregates/jobs
/api/v2/analytics/users/aggregates/query
/api/v2/analytics/users/aggregates/jobs
/api/v2/outbound/schedules/campaigns
/api/v2/outbound/schedules/campaigns/{campaignId}
/api/v2/outbound/schedules/sequences
/api/v2/outbound/schedules/sequences/{sequenceId}
/api/v2/outbound/schedules/messagingcampaigns
/api/v2/outbound/schedules/messagingcampaigns/{messagingCampaignId}
/api/v2/outbound/schedules/emailcampaigns
/api/v2/outbound/schedules/emailcampaigns/{emailCampaignId}
/api/v2/outbound/schedules/whatsappcampaigns
/api/v2/outbound/schedules/whatsappcampaigns/{whatsAppCampaignId}
/api/v2/outbound/contactlists/{contactListId}/contacts/search
/api/v2/outbound/contactlistfilters/preview
/api/v2/outbound/campaigns/{campaignId}/callback/schedule
/api/v2/outbound/contactlists/{contactListId}/contacts
/api/v2/outbound/contactlists/{contactListId}/contacts/{contactId}
/api/v2/outbound/contactlists/{contactListId}/contacts/bulk
/api/v2/outbound/callabletimesets
/api/v2/outbound/callabletimesets/{callableTimeSetId}
/api/v2/outbound/settings
/api/v2/outbound/attemptlimits
/api/v2/outbound/attemptlimits/{attemptLimitsId}
/api/v2/architect/schedulegroups
/api/v2/architect/schedulegroups/{scheduleGroupId}
/api/v2/scim/v2/groups
/api/v2/scim/v2/users
/api/v2/scim/v2/users/{userId}
/api/v2/scim/v2/groups/{groupId}
/api/v2/socialmedia/analytics/aggregates/jobs
/api/v2/socialmedia/analytics/messages/jobs
/api/v2/workforcemanagement/teams/{teamId}/adherence/historical
/api/v2/workforcemanagement/managementunits/{managementUnitId }/historicaladherencequery
/api/v2/workforcemanagement/adherence/historical
/api/v2/analytics/knowledge/aggregates/jobs
/api/v2/analytics/knowledge/aggregates/query
Issue References
PURE-6863
Contacts
@Ananya Singh
Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.