---
title: "Get time zone"
method: GET
path: "/v1/time_zones/{time_zone}"
tags: ["Time Zones"]
---

# Get time zone

`GET /v1/time_zones/{time_zone}`

## Request

- Base URL: `https://api.savvycal.com`
- URL: `https://api.savvycal.com/v1/time_zones/{time_zone}`
- Auth: one of:
  - OAuth 2
    - Authorization code: `/oauth/authorize`
    - Token URL: `/oauth/token`
  - HTTP bearer
  - HTTP bearer
- TypeScript: <https://skmtc.dev/savvycal/apis/savvycal-meetings-api/docs/v1/time_zones/:time_zone/get.ts> (a function with typed inputs; its response is checked against the schema)

## Path parameters

- `time_zone` string, required

## Query parameters

- `instant` string, date-time

## Response `200`

Success

- SingleTimeZoneResponse: Time zone information with localized names and DST details.
  - `abbreviation` string, required: Time zone abbreviation (e.g., 'CST', 'CDT').
  - `aliases` string[], required: Other IDs for the zone, such as `US/Central`.
  - `canonical` boolean, required: Whether this is the canonical time zone identifier in the IANA database.
  - `dst` boolean, required: Whether daylight saving time is in effect at `instant`.
  - `formatted_offset` string, required: Human-readable offset (e.g., '-06:00').
  - `generic_long_name` string, required: The generic name of the time zone's metazone (absent of any daylight saving time modifiers). For example, the generic name for US Central Time is Central Time, whereas the non-generic is either Central Daylight Time or Central Standard Time, depending on the time of year.
  - `golden` boolean, required: Whether the time zone is considered a [golden zone](https://unicode.org/reports/tr35/tr35-dates.html#Using_Time_Zone_Names) in the CLDR database.
  - `id` string, required: The IANA (Olson) time zone ID, such as `America/Chicago`.
  - `legacy` boolean, required: Whether the time zone is a "legacy" zone that does not conform to the standard Olson identifier format.
  - `long_name` string, required: The most specific name for the time zone's metazone, which may include daylight saving time modifiers at the specified instant. For example, the long name for US Central Time is either "Central Daylight Time" or "Central Standard Time", depending on the time of year.
  - `metazone` object, nullable: A metazone is a collection of time zones that share the same behavior and same name during some period. Each metazone represents a geographic region and is useful for determining commonly-used names for time zones. For example, the metazone for U.S. Central Time is `America_Central` and has the following long and short identifiers defined in the Unicode CLDR repository: ```javascript { "name": "America_Central", "long": { "current": "Central Standard Time", "daylight": "Central Daylight Time", "generic": "Central Time", "standard": "Central Standard Time" }, "short": { "current": "CST", "daylight": "CDT", "generic": "CT", "standard": "CST" }, "territories": ["001"] } ``` Some facts to note about metazones: - There are 126 metazones. - There are 93 metazones that map to a single time zone. - There are 34 metazones that map to multiple time zones. For example, the `America_Central` metazone includes 24 distinct time zones. - Every metazone has one [golden zone](https://unicode.org/reports/tr35/tr35-dates.html#Using_Time_Zone_Names), which "exemplifies" the metazone (and is tagged with territory `"001"`). - There are 64 canonical time zones not associated with a metazone.
    - `exemplar_city` string, nullable: The exemplar city designated for the metazone, if applicable (e.g. Chicago).
    - `long` object, nullable: A collection of generic and DST-specific "long" names (some or all might be `null`).
      - `current` string, nullable
      - `daylight` string, nullable
      - `generic` string, nullable
      - `standard` string, nullable
    - `name` string: The identifier for the metazone (e.g. America_Central).
    - `short` object, nullable: A collection of generic and DST-specific "short" names (some or all might be `null`).
      - `current` string, nullable
      - `daylight` string, nullable
      - `generic` string, nullable
      - `standard` string, nullable
    - `territories` string[]: Territory codes that use this metazone.
  - `offset` integer, required: Seconds offset from UTC at `instant`, including any daylight saving time shift.
  - `offset_std` integer, required: Seconds of daylight saving time shift at `instant`. Zero in standard time.
  - `offset_utc` integer, required: Seconds offset from UTC in standard time.
  - `period` object, required: The boundaries of the current zone period (e.g. either standard time or daylight saving time).
    - `from` string, date-time, nullable
    - `until` string, date-time, nullable
  - `windows_zone` object, nullable, required: Windows zones are names derived from the Microsoft Windows time zone mapping file (see [windowsZones.xml](https://github.com/unicode-org/cldr/blob/4667907abd60081c29f0b110623efc4ec545d844/common/supplemental/windowsZones.xml) in the CLDR repository). We use the zone names from this file as a fallback for `long_name` and `generic_long_name` fields when there does not exist a metazone name.
    - `name` string

## Other responses

- `401`: Unauthorized
- `404`: Not Found

---

[API](https://skmtc.dev/savvycal/apis/savvycal-meetings-api.md) - [All operations](https://skmtc.dev/savvycal/apis/savvycal-meetings-api/llms.txt) - [OpenAPI document](https://skmtc.dev/savvycal/apis/savvycal-meetings-api/revisions/398985d699a3?raw)