The Time Zone Tracker API is a robust service that allows users to retrieve time zone information based on specific geographic coordinates. This API is especially useful for applications that require accurate time management, such as scheduling tools, travel applications and event planning software. By providing detailed time zone data, the Time Zone Tracker API ensures that users have accurate information about local time, Daylight Saving Time (DST) settings, and general time zone characteristics.
When a user searches for information about a time zone, they typically submit the geographic coordinates (latitude and longitude) of a given location. The API processes this information and returns a response that includes several essential components. The key elements of this response are “dstOffset” and “rawOffset”, which represent time differences relative to Coordinated Universal Time (UTC). The “dstOffset” indicates any additional time differences applied during Daylight Saving Time, while the “rawOffset” reflects the standard time difference regardless of Daylight Saving Time.
In summary, the Time Zone Tracker API is an invaluable resource for users wishing to integrate accurate time zone information into their applications. With its extensive data on time offsets, raw offsets, time zone IDs and user-friendly names, the API simplifies the complexities of time zone management, enabling applications to deliver a seamless experience to users around the world. As global connectivity increases, the need for reliable time zone data will continue to grow, making the Time Zone Tracker API an essential asset for users.
To use this endpoint you must indicate a latitude, longitude and a timestamp in the parameters.
Timezone Data - Endpoint Features
| Object | Description |
|---|---|
location |
[Required] Indicates a timestamp |
timestamp |
[Required] Indicates a latitude and longitude |
Continue with Google
Continue with Github
{
"dstOffset" : 0,
"rawOffset" : -28800,
"status" : "OK",
"timeZoneId" : "America/Los_Angeles",
"timeZoneName" : "Pacific Standard Time"
}
curl --location --request GET 'https://zylalabs.com/api/5264/time+zone+tracker+api/6783/timezone+data?location=39.6034810,-119.6822510×tamp=1331161200' --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.
To use this API, users must indicate a latitude, longitude and a timestamp.
There are different plans suits everyone including a free trial for small amount of requests, but it’s rate is limit to prevent abuse of the service.
The Time Zone Tracker API offers detailed time zone information, including offsets, names, and daylight saving time adjustments for specific geographical locations.
The Time Zone Tracker API requires latitude, longitude, and a timestamp as input. It returns offsets, status, time zone ID, and a human-readable time zone name.
Besides the number of API calls per month, there are no other limitations.
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:
143ms
Service Level:
100%
Response Time:
482ms
Service Level:
100%
Response Time:
87ms
Service Level:
100%
Response Time:
334ms
Service Level:
100%
Response Time:
109ms
Service Level:
100%
Response Time:
388ms
Service Level:
100%
Response Time:
87ms
Service Level:
100%
Response Time:
680ms
Service Level:
100%
Response Time:
535ms
Service Level:
100%
Response Time:
776ms
Service Level:
100%
Response Time:
2,307ms
Service Level:
100%
Response Time:
448ms
Service Level:
100%
Response Time:
170ms
Service Level:
100%
Response Time:
420ms
Service Level:
100%
Response Time:
88ms
Service Level:
100%
Response Time:
364ms
Service Level:
100%
Response Time:
184ms
