Sign in

99e0701a73aa

latestOpenAPI 3.1.02026-08-0420183200.9 KB
Geospatial

Get time zone information for any point on earth.

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

get/tz/lookup/v1

Query parameters

latnumber double required

The latitude of the point you are interested in.

lngnumber double required

The longitude of the point you are interested in.

timestampinteger

The UNIX timestamp at which the UTC and DST offsets will be calculated. This defaults to the present time. This endpoint is not necessarily guaranteed to be accurate for timestamps that occurred in the past. Time zone geographic boundaries change over time, so if the point you are querying for was previously in a different time zone, historical results will not be accurate. If, however, the point has been in the same geographic time zone for a very long time (ex: America/New_York), the historical data may be accurate for 100+ years in the past (depending on how far back the IANA TZDB rules have been specified).

Response

The time zone information and local time.

tz_idstring 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_offsetinteger required

The base offset, in seconds, from UTC that is normally in effect for this time zone.

dst_offsetinteger 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.

timestampinteger 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_timestampstring 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_timestampstring 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.

Example response

{
  "tz_id": "Europe/Zurich",
  "base_utc_offset": 3600,
  "dst_offset": 3600,
  "timestamp": 1749479378,
  "local_rfc_2822_timestamp": "Mon, 9 Jun 2025 16:29:38 +0200",
  "local_rfc_3389_timestamp": "2025-06-09T16:29:38+02:00"
}