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
{"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 commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The Get Timezone endpoint returns timezone information based on latitude and longitude coordinates. The response includes the timezone identifier, UTC offset, and Daylight Saving Time (DST) offset.
The key fields in the response data are `timeZoneId` (the identifier for the timezone), `rawOffset` (the UTC offset in seconds), and `dstOffset` (the additional offset during Daylight Saving Time in seconds).
The response data is structured in JSON format, containing key-value pairs. For example, a typical response might look like: `{"dstOffset":0,"rawOffset":-28800,"timeZoneId":"America/Vancouver","timeZoneName":"Pacific Standard Time"}`.
The Get Timezone endpoint accepts latitude and longitude as parameters. Optionally, a timestamp can be included to account for Daylight Saving Time adjustments.
The endpoint provides information on the timezone identifier, UTC offset, and DST offset for any given geographic coordinates, allowing applications to accurately reflect local time.
Data accuracy is maintained through regular updates from reliable geographic and timezone databases, ensuring that changes in timekeeping practices, such as DST adjustments, are reflected promptly.
Typical use cases include displaying local times in travel apps, ensuring correct scheduling in multi-timezone environments, and providing accurate delivery estimates in e-commerce applications.
Users can utilize the returned data by integrating it into their applications to display local times, adjust scheduling features, or provide location-specific information based on the timezone data received.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key 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.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
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. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
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.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
482ms
Service Level:
100%
Response Time:
226ms
Service Level:
100%
Response Time:
134ms
Service Level:
100%
Response Time:
485ms
Service Level:
100%
Response Time:
2,518ms
Service Level:
100%
Response Time:
106ms
Service Level:
100%
Response Time:
195ms
Service Level:
100%
Response Time:
86ms
Service Level:
100%
Response Time:
94ms
Service Level:
100%
Response Time:
683ms