The REST API endpoint for extension business hours (/restapi/v1.0/account/{accountId}/extension/{extensionId}/business-hours) returns weekly schedule ranges (for example, 08:00 to 17:00) but omits the timezone. We request that the timezone object or identifier be included directly in the business hours API response.

Current Problem:
In an enterprise account spanning multiple time zones and sites, schedule intervals returned without an explicit timezone create operational ambiguity. Extension regional settings and parent site timezones can differ, so inferring the timezone from a separate API call is unreliable and requires redundant queries across hundreds of extensions, call queues, and IVR menus.

Proposed Solution:
Include the standard RingCentral timezone object (id, name, and description) in the business hours response body alongside the schedule object.

Business Impact:
We run nightly configuration exports and automated routing validation across our account. Including timezone in the business hours payload ensures accurate schedule evaluation, eliminates extra API calls, and aligns the API response with the information visible in the Admin Portal.