Global Timezone Locator API provides a simple and efficient way to retrieve accurate time zone information for any geographic location based on latitude and longitude. This API is perfect for applications requiring precise time data, such as scheduling systems, logistics platforms, or travel planning tools. By specifying the latitude, longitude, and a timestamp, you can obtain detailed information such as Daylight Savings Time (DST) offset, raw UTC offset, and the corresponding time zone ID and name. The API handles complex time zone calculations and daylight savings adjustments, ensuring accurate results regardless of the location or time of year. Whether you're developing global apps or integrating localized time data, this API delivers fast and reliable results, helping streamline your projects. Ideal for developers working on international apps, this tool ensures precise time zone management for any scenario.
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 Data - 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/5784/global+timezone+locator+api/7521/get+timezone+data?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 retrieve accurate timezone details including Daylight Savings Time (DST) offset, raw UTC offset, time zone ID, and time zone name for any geographic location based on its latitude and longitude.
You specify the location by providing the latitude and longitude coordinates in your API request. This allows the API to calculate the corresponding timezone information for that specific geographic point.
Yes, the Global Timezone Locator API automatically handles Daylight Savings Time adjustments, ensuring that the timezone information is accurate regardless of the time of year.
The API is ideal for applications that require precise time data, such as scheduling systems, logistics platforms, travel planning tools, and any global applications that need accurate time zone management.
Yes, the API is designed for developers working on international applications, providing fast and reliable timezone information to streamline projects across different geographic locations.
The API returns timezone information including the timezone ID, timezone name, UTC offset, and DST offset for specified latitude and longitude coordinates.
The key fields in the response include `timeZoneId`, `timeZoneName`, `rawOffset`, and `dstOffset`, which provide essential timezone details for the given location.
The response data is structured in JSON format, with key-value pairs representing the timezone details. For example, `{"dstOffset":0,"rawOffset":28800,"timeZoneId":"Asia/Shanghai","timeZoneName":"China Standard Time"}`.
The endpoint accepts three parameters: `lat` (latitude), `lng` (longitude), and `timestamp` (specific time), allowing users to customize their requests for precise timezone data.
The endpoint provides information on the timezone ID, name, UTC offset, and DST offset, enabling users to understand the time context for any geographic location.
Data accuracy is maintained through regular updates from reliable sources, ensuring that timezone information reflects current standards and adjustments, including Daylight Savings Time.
Typical use cases include scheduling events across time zones, managing logistics for global operations, and developing travel applications that require accurate local time information.
Users can utilize the returned data to display local times, schedule meetings across different regions, or adjust application functionalities based on the user's timezone, enhancing user experience.
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:
226ms
Service Level:
100%
Response Time:
134ms
Service Level:
100%
Response Time:
482ms
Service Level:
100%
Response Time:
106ms
Service Level:
100%
Response Time:
2,518ms
Service Level:
100%
Response Time:
485ms
Service Level:
100%
Response Time:
86ms
Service Level:
100%
Response Time:
448ms
Service Level:
100%
Response Time:
535ms
Service Level:
100%
Response Time:
299ms
Service Level:
100%
Response Time:
1,138ms
Service Level:
100%
Response Time:
171ms
Service Level:
100%
Response Time:
2,989ms
Service Level:
100%
Response Time:
2,774ms
Service Level:
89%
Response Time:
345ms
Service Level:
100%
Response Time:
193ms
Service Level:
100%
Response Time:
387ms
Service Level:
100%
Response Time:
449ms
Service Level:
100%
Response Time:
449ms