TimeZone Locator API provides precise timezone details based on geographic coordinates. By entering latitude, longitude, and an optional timestamp, this API gives you the raw UTC offset, DST offset, and the exact timezone name and ID. Whether you're building global scheduling platforms, time-sensitive logistics systems, or travel apps, this API ensures accurate time zone calculations. Handle daylight savings time changes effortlessly and deliver the most reliable time-related data to your users in real-time. Perfect for applications needing timezone precision for international users.
Send a GET request with lat, lng, and timestamp. The API returns timezone ID, name, UTC offset, and DST offset for the specified coordinates.
Get TimeZone Details - Endpoint Features
| Object | Description |
|---|---|
lat |
[Required] Latitude |
lng |
[Required] Longitude |
timestamp |
[Required] The desired time as **seconds **since midnight, January 1, 1970 UTC. |
{"dstOffset":0,"rawOffset":28800,"timeZoneId":"Asia/Shanghai","timeZoneName":"China Standard Time"}
curl --location --request GET 'https://zylalabs.com/api/5785/timezone+locator+api/7522/get+timezone+details?lat=49.282409&lng=123.045868×tamp=1646179205' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
You can obtain precise timezone details including the raw UTC offset, DST offset, timezone name, and timezone ID based on geographic coordinates.
To use the API, you need to provide the latitude and longitude of the location you are interested in. Optionally, you can also provide a timestamp to get accurate DST information.
UTC (Coordinated Universal Time) offset indicates the difference in hours and minutes from UTC time, while DST (Daylight Saving Time) offset shows the additional time adjustment during DST periods. They are important for accurate time calculations across different regions.
Yes, the API can handle daylight savings time changes by providing the correct DST offset based on the timestamp you supply along with the geographic coordinates.
Applications such as global scheduling platforms, time-sensitive logistics systems, and travel apps can greatly benefit from the accurate timezone calculations provided by the API.
The API returns timezone details including the timezone ID, timezone name, raw UTC offset, and DST offset based on the provided geographic coordinates and optional timestamp.
The key fields in the response include `timeZoneId`, `timeZoneName`, `rawOffset`, and `dstOffset`, which provide essential information about the timezone and its offsets.
The response data is structured in JSON format, with key-value pairs representing the timezone details. For example: `{"timeZoneId":"Asia/Shanghai", "timeZoneName":"China Standard Time", "rawOffset":28800, "dstOffset":0}`.
The endpoint accepts three parameters: `lat` (latitude), `lng` (longitude), and an optional `timestamp` to retrieve accurate DST information for the specified location.
The TimeZone Locator API covers global timezone data, providing accurate information for any location on Earth based on geographic coordinates.
Data accuracy is maintained through regular updates from reliable sources, ensuring that timezone information reflects current standards and practices, including DST changes.
Typical use cases include scheduling applications, travel planning tools, and logistics systems that require precise time calculations across different time zones.
Users can utilize the returned data to display local times, schedule events accurately, and manage time-sensitive operations by integrating the timezone information into their applications.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
102ms
Service Level:
100%
Response Time:
482ms
Service Level:
100%
Response Time:
86ms
Service Level:
100%
Response Time:
195ms
Service Level:
100%
Response Time:
226ms
Service Level:
100%
Response Time:
106ms
Service Level:
100%
Response Time:
2,518ms
Service Level:
100%
Response Time:
189ms
Service Level:
100%
Response Time:
174ms
Service Level:
100%
Response Time:
485ms
Service Level:
100%
Response Time:
3,513ms
Service Level:
100%
Response Time:
3,110ms
Service Level:
100%
Response Time:
3,468ms
Service Level:
100%
Response Time:
3,386ms
Service Level:
100%
Response Time:
3,383ms
Service Level:
50%
Response Time:
5,254ms
Service Level:
33%
Response Time:
1,570ms
Service Level:
67%
Response Time:
6,744ms
Service Level:
50%
Response Time:
1,673ms
Service Level:
50%
Response Time:
4,387ms