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 commitments. One click upgrade/downgrade or cancellation. No questions asked.
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.
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.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the βX-Zyla-API-Calls-Monthly-Remainingβ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
143ms
Service Level:
100%
Response Time:
189ms
Service Level:
100%
Response Time:
195ms
Service Level:
100%
Response Time:
86ms
Service Level:
100%
Response Time:
109ms
Service Level:
100%
Response Time:
482ms
Service Level:
100%
Response Time:
106ms
Service Level:
100%
Response Time:
164ms
Service Level:
100%
Response Time:
334ms
Service Level:
100%
Response Time:
244ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
12,425ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
4,452ms
Service Level:
98%
Response Time:
0ms