# Client API: Container Apps: Timezones

> The 1 Client API operations for timezones.

Source: https://docs.coritan.com/api/reference/client/container-apps/timezones/

Part of [Container Apps](/api/reference/client/container-apps/).

## Operations

| Method | Path | Summary |
| --- | --- | --- |
| GET | [`/api/v1/client/timezones`](#op-get-api-v1-client-timezones) | Every zone this platform can resolve, west to east, with its old names |

### Every zone this platform can resolve, west to east, with its old names {#op-get-api-v1-client-timezones}

`GET /api/v1/client/timezones`

Every zone this platform can resolve, west to east, with its old names.

A picker built from the browser offers names the API then rejects: Chrome
reports CLDR's ids, and for a dozen zones those are the pre-rename IANA
names, which only resolve where the backward-compatibility links are
installed. This is the list the API will actually accept, so a form built
from it cannot drift from the server.

Authentication: an access token, sent as `Authorization: Bearer <token>`.

#### Responses

| Status | Meaning |
| --- | --- |
| `200` | Success. |

Fields of a `200` response:

| Field | Type |
| --- | --- |
| `version` | string |
| `zones` | array of TimezoneOption |
| `zones[].name` | string |
| `zones[].region` | string |
| `zones[].city` | string |
| `zones[].offset` | string |
| `zones[].offset_minutes` | integer |
| `aliases` | Aliases |