The Timezone by Coordinates API is a powerful tool that enables developers to easily retrieve the timezone, Daylight Saving Time (DST) offset, and UTC offset of a location based on its latitude and longitude coordinates. This information can be invaluable for applications that require accurate timekeeping, such as scheduling software, travel apps, and weather services.
The API uses the latitude and longitude coordinates of a location to determine its timezone. It then returns a response containing the timezone identifier, UTC offset, and DST offset for that location. The timezone identifier is a string that uniquely identifies the timezone, such as "America/Los_Angeles" for Pacific Standard Time in the United States. The UTC offset is the difference between the location's local time and Coordinated Universal Time (UTC), expressed in hours. The DST offset is the additional offset applied during Daylight Saving Time, expressed in hours.
Using the Timezone by Coordinates API is simple and straightforward. Developers can make a GET request to the API endpoint, passing in the latitude and longitude coordinates of the location they want to query. The API then returns a JSON response containing the timezone information for that location.
One of the primary benefits of the Timezone by Coordinates API is that it eliminates the need for developers to manually calculate timezones and offsets based on latitude and longitude coordinates. This can be a time-consuming and error-prone process, especially for locations that observe DST. By using the API, developers can be confident that they are getting accurate and reliable timezone information for any location in the world.
The Timezone by Coordinates API can be used in a variety of applications. For example, travel apps can use the API to display the local time and weather for a user's current location, or for a destination they are planning to visit. Scheduling software can use the API to ensure that appointments and events are displayed in the correct timezone for each participant. Weather services can use the API to display weather information for a specific location based on its time zone.
In summary, the Timezone by Coordinates API is a powerful tool that provides developers with accurate and reliable timezone information for any location in the world. Its ease of use and flexibility make it a valuable asset for a wide range of applications.
Pass latitude, longitude, and timestamp and receive the time zone
Travel apps: Travel apps can use the API to determine the timezone of a user's current location or a destination they are planning to visit. This information can be used to display the local time and weather, as well as provide recommendations for activities and events based on the time of day.
Scheduling software: Scheduling software can use the API to ensure that appointments and events are displayed in the correct timezone for each participant. This can help to avoid confusion and scheduling conflicts, especially for teams or organizations that operate across multiple time zones.
E-commerce: E-commerce sites can use the API to display delivery times and dates based on the timezone of the customer's shipping address. This can help to provide more accurate delivery estimates and improve customer satisfaction.
Financial services: Financial services companies can use the API to accurately timestamp financial transactions and to comply with regulatory requirements related to timekeeping and reporting.
Weather services: Weather services can use the API to display weather information for a specific location based on its time zone. This can help users to plan outdoor activities or travel, as well as provide insights into weather patterns and trends in different regions.
Besides the number of API calls, there is no other limitation
Get the timezone of the coordinate location.
Get Timezone - Endpoint Features
| Object | Description |
|---|---|
lat |
[Required] Latitude |
lng |
[Required] Longitude |
timestamp |
[Required] The desired time as **seconds **since midnight, January 1, 1970 UTC. |
Continue with Google
Continue with Github
{"dstOffset":0,"rawOffset":-28800,"timeZoneId":"America/Vancouver","timeZoneName":"Pacific Standard Time"}
curl --location --request GET 'https://zylalabs.com/api/1783/timezone+by+coordinates+api/1429/get+timezone?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.
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, look at the ‘X-Zyla-API-Calls-Monthly-Remaining’ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.
To see the maximum number of API requests your plan allows, check the ‘X-Zyla-RateLimit-Limit’ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.
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 3600, it means 3600 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 let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
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 trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
100%
Response Time:
482ms
Service Level:
100%
Response Time:
143ms
Service Level:
100%
Response Time:
334ms
Service Level:
100%
Response Time:
547ms
Service Level:
100%
Response Time:
388ms
Service Level:
100%
Response Time:
109ms
Service Level:
100%
Response Time:
153ms
Service Level:
100%
Response Time:
1,530ms
Service Level:
100%
Response Time:
87ms
Service Level:
100%
Response Time:
759ms
Service Level:
100%
Response Time:
570ms
Service Level:
100%
Response Time:
1,355ms
Service Level:
100%
Response Time:
767ms
Service Level:
100%
Response Time:
624ms
Service Level:
100%
Response Time:
514ms
Service Level:
100%
Response Time:
2,307ms
Service Level:
100%
Response Time:
974ms
