The Global Time Mapper API acts as a reliable bridge between applications and the intricate realm of time zones. From bustling metropolises to the most remote corners of the world, this API provides a unified solution for accurate local time zone data. By simply entering a city name or latitude/longitude coordinates, users can access essential information such as time offset, abbreviated time zone name and more. This wealth of data ensures that applications maintain synchronization with various regions, enabling seamless scheduling, event coordination and communication.
One of the most commendable features of the Global Time Mapper API is its simple integration process. Users can seamlessly integrate time zone functionality into their applications, whether they are mobile apps, global event platforms, meeting schedulers or collaboration tools. The API's simple endpoints and response formats allow users to quickly integrate time zone data, thus enriching the user experience with accurate and contextually relevant time information.
Accuracy is paramount when working with time zones, and the Global Time Mapper API achieves this based on robust data sources. By leveraging authoritative databases and time zone repositories, the API ensures that users receive up-to-date and accurate information. This accuracy is especially crucial for applications that manage critical schedules, financial transactions or travel arrangements, where discrepancies can cause major disruptions.
The real-time functionality of the API ensures that applications have the most up-to-date time zone information. By providing real-time data updates, the API reduces the risk of outdated information causing confusion or errors in scheduling, communication and global coordination.
Compatibility is another outstanding feature of the Global Time Mapper API. It integrates seamlessly with a wide range of programming languages and frameworks, making it easy for users to incorporate time zone functionality into their existing technology stacks. In addition, the API's comprehensive documentation guides developers through endpoints, request formats and response structures, minimizing the learning curve and facilitating rapid integration.
In conclusion, the Global Time Mapper API is emerging as an essential solution for users, businesses and developers dealing with the complexity of global time zones. Its accuracy, easy integration and real-time data updates make it an invaluable tool for applications in a variety of industries. By providing accurate local time zone data based on city names or geographic coordinates, the API enables all users to streamline programming, improve communication and maintain synchronization in an interconnected world. As businesses continue to expand globally, the Global Time Mapper API is a testament to the role of technology in simplifying and improving cross-border operations.
It will receive parameters and provide you with a JSON.
Travel applications: Travel planning platforms can integrate the API to display local times for various destinations, helping travelers adjust their schedules and overcome jet lag.
Global communication: Messaging and collaboration tools can use the API to display the local time zone of team members or contacts, facilitating real-time communication in different parts of the world.
Remote work coordination: Remote work tools can display the local times of team members' locations, helping distributed teams coordinate meetings and tasks efficiently.
E-commerce platforms: E-commerce websites can display local times for customer service and order processing, creating a better user experience and reducing response time.
World clock applications: World clock applications can provide users with accurate local times for multiple cities simultaneously, assisting in tracking time differences.
Besides the number of API calls per month, there are no other limitations.
To use this endpoint you must provide the name of a city and its country in the parameter.
TimeZone by country and city - Endpoint Features
Object | Description |
---|---|
cityCountry |
[Required] |
{"data":{"originalQuery":"Toronto, Canada","name":"Toronto, ON","timeZone":"America\/Toronto","utc_offset":"-5:00","generic_time_zone_name":"Eastern Standard Time","utc_offset_with_dst":"-4:00","generic_time_zone_name_with_dst":"Eastern Daylight Time","timezone_current_local_time":"2023-08-15T09:23:52.223273-04:00"}}
curl --location --request GET 'https://zylalabs.com/api/2440/global+time+mapper+api/2392/timezone+by+country+and+city?cityCountry=Toronto, Canada' --header 'Authorization: Bearer YOUR_API_KEY'
To use this endpoint you must indicate coordinates such as latitude and longitude in the parameter.
TimeZone by coordinates - Endpoint Features
Object | Description |
---|---|
latitude |
[Required] |
longitude |
[Required] |
{"data":{"originalQuery":{"latitude":"61.768335","longitude":"-158.808765"},"timeZone":"America\/Anchorage","utc_offset":"-9:00","generic_time_zone_name":"Alaskan Standard Time","utc_offset_with_dst":"-8:00","generic_time_zone_name_with_dst":"Alaskan Daylight Time","timezone_current_local_time":"2023-08-15T05:25:07.402494-08:00"}}
curl --location --request GET 'https://zylalabs.com/api/2440/global+time+mapper+api/2393/timezone+by+coordinates?latitude=61.768335&longitude=-158.808765' --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 the user must indicate coordinates or a country and a city.
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.
Zyla provides a wide range of integration methods for almost all programming languages. You can use these codes to integrate with your project as you need.
It is an API that provides users with information about time zones through coordinates or countries and cities.
Each endpoint returns JSON data containing local time zone information, including the time zone name, UTC offset, and current local time. For example, the response includes fields like "timeZone," "utc_offset," and "timezone_current_local_time."
Key fields in the response include "originalQuery," which shows the input city or coordinates, "timeZone" for the time zone identifier, "utc_offset" for standard time offset, and "timezone_current_local_time" for the current local time.
The "GET TimeZone by country and city" endpoint requires a city name and country, while the "GET TimeZone by coordinates" endpoint requires latitude and longitude values. Users must provide these parameters to receive accurate time zone data.
The response data is structured in a JSON format with a "data" object containing relevant fields. Each field provides specific information, such as time zone details and current local time, making it easy to parse and utilize in applications.
The Global Time Mapper API sources its data from authoritative databases and time zone repositories, ensuring high accuracy and reliability. This helps maintain up-to-date information for users across various regions.
Typical use cases include travel applications displaying local times for destinations, remote work tools coordinating meetings across time zones, and e-commerce platforms providing local customer service hours, enhancing user experience.
Users can customize requests by specifying different city names, countries, or geographic coordinates. This flexibility allows for tailored queries to retrieve specific time zone information relevant to their needs.
If a query returns partial or empty results, users should verify the accuracy of the input parameters. Ensuring correct spelling of city names or valid coordinates can help improve the chances of receiving complete data.
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:
109ms
Service Level:
100%
Response Time:
87ms
Service Level:
100%
Response Time:
143ms
Service Level:
100%
Response Time:
106ms
Service Level:
100%
Response Time:
86ms
Service Level:
100%
Response Time:
448ms
Service Level:
100%
Response Time:
662ms
Service Level:
100%
Response Time:
482ms
Service Level:
100%
Response Time:
195ms
Service Level:
100%
Response Time:
571ms
Service Level:
100%
Response Time:
2,379ms
Service Level:
100%
Response Time:
3,585ms
Service Level:
100%
Response Time:
630ms
Service Level:
100%
Response Time:
2,991ms
Service Level:
100%
Response Time:
1,793ms
Service Level:
100%
Response Time:
344ms
Service Level:
100%
Response Time:
2,628ms
Service Level:
100%
Response Time:
1,879ms
Service Level:
100%
Response Time:
2,315ms
Service Level:
92%
Response Time:
1,362ms