GeoTime API delivers reliable timezone information by processing geographic coordinates to give you the current UTC offset, Daylight Savings Time (DST) changes, and the corresponding time zone ID and name. By specifying a location through latitude and longitude, this API handles complex time zone and daylight savings adjustments, ensuring precise and accurate time data. Whether you're creating international applications, scheduling systems, or apps for global travelers, GeoTime API simplifies time zone management with real-time and historical data, enabling your app to work seamlessly across time zones.
Send a GET request with lat, lng, and timestamp. The API returns timezone ID, name, UTC offset, and DST offset for the specified coordinates.
Locate TimeZone - 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/5786/geotime+api/7523/locate+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 GeoTime API is a service that allows users to efficiently retrieve timezone, UTC, and Daylight Savings Time (DST) information based on geographic coordinates (latitude and longitude).
To use the GeoTime API, you need to provide the latitude and longitude of the location you are interested in. The API will return the current UTC offset, DST changes, and the corresponding time zone ID and name.
Yes, the GeoTime API is designed to handle complex time zone and Daylight Savings Time adjustments, ensuring that you receive accurate time data regardless of seasonal changes.
The GeoTime API is ideal for international applications, scheduling systems, and apps for global travelers, as it simplifies time zone management with real-time and historical data.
Yes, the GeoTime API provides both real-time and historical timezone data, allowing you to access time information for past dates and times.
The Locate TimeZone endpoint returns timezone ID, timezone name, UTC offset, and DST offset based on the provided latitude, longitude, and optional timestamp.
The key fields in the response data include `timeZoneId`, `timeZoneName`, `rawOffset`, and `dstOffset`, which provide essential timezone and offset information.
The response data is structured in JSON format, with key-value pairs representing the timezone ID, name, UTC offset, and DST offset, making it easy to parse and utilize.
The parameters for the Locate TimeZone endpoint include `lat` (latitude), `lng` (longitude), and `timestamp` (optional), allowing users to specify the location and time for accurate results.
Users can customize their requests by providing specific latitude and longitude values, and optionally including a timestamp to retrieve timezone information for a particular date and time.
The GeoTime API sources its data from reliable geographic and timezone databases, ensuring accurate and up-to-date timezone information for various locations worldwide.
Typical use cases include scheduling events across time zones, displaying local times for users in different regions, and developing applications that require accurate time zone management for global users.
If the API returns partial or empty results, check the provided latitude and longitude for accuracy. Ensure that the coordinates correspond to a valid location, as some remote areas may not have timezone data.
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:
195ms
Service Level:
100%
Response Time:
101ms
Service Level:
100%
Response Time:
226ms
Service Level:
100%
Response Time:
174ms
Service Level:
100%
Response Time:
448ms
Service Level:
100%
Response Time:
1,541ms
Service Level:
100%
Response Time:
482ms
Service Level:
100%
Response Time:
48ms
Service Level:
100%
Response Time:
2,518ms
Service Level:
100%
Response Time:
134ms
Service Level:
100%
Response Time:
332ms
Service Level:
100%
Response Time:
482ms
Service Level:
100%
Response Time:
6,148ms
Service Level:
100%
Response Time:
1,775ms
Service Level:
100%
Response Time:
568ms
Service Level:
100%
Response Time:
337ms
Service Level:
100%
Response Time:
2,081ms
Service Level:
100%
Response Time:
355ms
Service Level:
100%
Response Time:
132ms
Service Level:
100%
Response Time:
666ms