---
title: "Get time zone information for any point on earth."
method: GET
path: "/tz/lookup/v1"
tags: ["Geospatial"]
---

# Get time zone information for any point on earth.

`GET /tz/lookup/v1`

Retrieve the time zone identifier, standard UTC offset, special offset (such as DST), and the localized time in several common formats.

## Query parameters

- `lat` number, double, required
- `lng` number, double, required
- `timestamp` integer

## Response `200`

The time zone information and local time.

- TzResponse
  - `tz_id` string, required — The canonical time zone ID. In the event that multiple time zones could be returned, the first one from the Unicode CLDR timezone.xml is returned.
  - `base_utc_offset` integer, required — The base offset, in seconds, from UTC that is normally in effect for this time zone.
  - `dst_offset` integer, required — The special offset, in seconds, from UTC that is in effect for this time zone as of the queried timestamp (defaults to now). If no additional offsets are in effect, this value is zero. This typically reflects Daylight Saving Time, but may indicate other special offsets. To get the total offset in effect, add `dst_offset` and `utc_offset` together. NOTE: This field can be somewhat confusing. We recommend switching to the v2 endpoint and using the is_dst filed if you need to identify whether DST is being observed.
  - `timestamp` integer, required — Integer non-leap seconds since January 1, 1970 (UNIX timestamp). If present, offsets will be calculated as of this time. Otherwise, offsets will be effective as of the time of the query.
  - `local_rfc_2822_timestamp` string, nullable — The local time expressed as an RFC 2822 timestamp (e.g. Tue, 1 Jun 2003 10:52:37 -0500). If a timestamp is included in the request, it will be localized here. Otherwise, this will reflect the time of the request. NOTE: RFC 2822 is more restrictive than other formats and cannot represent all dates.
  - `local_rfc_3389_timestamp` string, required — The local time expressed as an RFC 3389 (ISO 8601) timestamp (e.g. 2003-06-01T10:52:37+02:00). If a timestamp is included in the request, it will be localized here. Otherwise, this will reflect the time of the request.

## Other responses

- `400` — Bad request
- `404` — Time zone not found

---

[API](https://skmtc.net/stadiamaps/apis/stadia-maps-geospatial-apis.md) · [All operations](https://skmtc.net/stadiamaps/apis/stadia-maps-geospatial-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/stadiamaps/stadia-maps-geospatial-apis/revisions/99e0701a73aa/schema)