Global Time Locator API

The Global Time Locator API offers precise time zone details, including historical data, facilitating seamless integration into global applications.

About the API:  

The Global Time Locator API is an essential resource for users who want to seamlessly integrate accurate and up-to-date time zone information into their applications, websites or services. In our globally connected digital environment, where real-time interactions cross multiple regions, accurate time zone data is critical for tasks ranging from scheduling events to coordinating international communications.

In essence, the Global Time Locator API provides users with a comprehensive repository of time zone data from around the world. This database contains vital information such as time offsets and unique identifiers for each time zone. By programmatically accessing this data, users can ensure that their applications present accurate and synchronized time information, catering to users in various geographic regions.

A notable feature of the Global Time Locator API is its ability to retrieve the current time for specific locations. Users can seamlessly query the API for real-time information from any time zone, allowing them to provide users with accurate and synchronized time data based on their geographic preferences.

In addition, the Global Time Locator API simplifies conversion between different time zones. Developers can effortlessly transform time stamps from one time zone to another, ensuring consistency of time-related data across global applications. This functionality is essential in industries such as business and finance, where time accuracy and synchronization are paramount.

In addition, users can leverage the Global Time Locator API to implement advanced features such as automatic time zone detection. By discerning a user's geographic location through their IP address or other means, applications can dynamically adjust the displayed time zone, offering users a seamless and personalized experience.

In conclusion, the Global Time Locator API is an essential tool for users facing the complexities of global time management in their applications. This API enables users to develop applications that deftly handle time-related information in various regions, fostering accurate and synchronized user experiences on a global scale.

 

What this API receives and what your API provides (input/output)?

It will receive parameters and provide you with a JSON.

 

What are the most common uses cases of this API?

  1. Event Scheduling: Ensure accurate scheduling of events across different time zones, helping users coordinate meetings, conferences, or webinars globally.

    International Business Applications: Facilitate global business operations by displaying accurate local times for various locations, aiding in communication and project management.

    Travel and Booking Platforms: Enhance user experience by displaying local times for destination cities, assisting travelers in planning activities and bookings.

    Finance and Trading Applications: Implement precise time zone conversions for financial transactions, market openings, and trading activities across global markets.

    Collaborative Tools: Optimize collaboration in teams spread across different regions by displaying synchronized time zone information for project deadlines and communication.

     

Are there any limitations to your plans?

Besides the number of API calls available for the plan, there are no other limitations.

API Documentation

Endpoints


To use this endpoint just run it and you will get all the times zones available.



                                                                            
GET https://zylalabs.com/api/3949/global+time+locator+api/4697/all+times+zones
                                                                            
                                                                        

Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            [
    {
        "Id": 33,
        "TimeZone": "Anywhere on Earth",
        "Abbreviation": "AoE",
        "Location": "Pacific",
        "Offset": "UTC -12"
    },
    {
        "Id": 228,
        "TimeZone": "Wallis and Futuna Time",
        "Abbreviation": "WFT",
        "Location": "Pacific",
        "Offset": "UTC +12"
    },
    {
        "Id": 243,
        "TimeZone": "Yekaterinburg Time",
        "Abbreviation": "YEKT",
        "Location": "Asia",
        "Offset": "UTC +5"
    },
    {
        "Id": 8,
        "TimeZone": "Atlantic Daylight TimeADST – Atlantic Daylight Saving TimeAST – Atlantic Summer TimeHAA – Heure Avancée de l'Atlantique (French)",
        "Abbreviation": "ADT",
        "Location": "North AmericaAtlantic",
        "Offset": "UTC -3"
    },
    {
        "Id": 38,
        "TimeZone": "Brasília TimeBT – Brazil TimeBT – Brazilian Time",
        "Abbreviation": "BRT",
        "Location": "South America",
        "Offset": "UTC -3"
    },
    {
        "Id": 180,
        "TimeZone": "Pyongyang TimePYST – Pyongyang Standard Time",
        "Abbreviation": "PYT",
        "Location": "Asia",
        "Offset": "UTC +8:30"
    }
]
                                                                                                                                                                                                                    
                                                                                                    

All Times Zones - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/3949/global+time+locator+api/4697/all+times+zones' --header 'Authorization: Bearer YOUR_API_KEY' 


    

To use this endpoint you must indicate a location in the parameter.



                                                                            
GET https://zylalabs.com/api/3949/global+time+locator+api/4698/time+zone+by+location
                                                                            
                                                                        

Time zone by location - Endpoint Features

Object Description
location [Required]
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            [
    {
        "Id": 8,
        "TimeZone": "Atlantic Daylight TimeADST – Atlantic Daylight Saving TimeAST – Atlantic Summer TimeHAA – Heure Avancée de l'Atlantique (French)",
        "Abbreviation": "ADT",
        "Location": "North AmericaAtlantic",
        "Offset": "UTC -3"
    },
    {
        "Id": 13,
        "TimeZone": "Alaska Daylight TimeADST – Alaska Daylight Saving Time",
        "Abbreviation": "AKDT",
        "Location": "North America",
        "Offset": "UTC -8"
    },
    {
        "Id": 14,
        "TimeZone": "Alaska Standard TimeAT – Alaska Time",
        "Abbreviation": "AKST",
        "Location": "North America",
        "Offset": "UTC -9"
    },
    {
        "Id": 25,
        "TimeZone": "Atlantic Standard TimeAT – Atlantic TimeAST – Tiempo Estándar del Atlántico  (Spanish)HNA – Heure Normale de l'Atlantique (French)",
        "Abbreviation": "AST",
        "Location": "North AmericaAtlanticCaribbean",
        "Offset": "UTC -4"
    },
    {
        "Id": 26,
        "TimeZone": "Atlantic Time",
        "Abbreviation": "AT",
        "Location": "North AmericaAtlantic",
        "Offset": "UTC -4:00 / -3:00"
    },
    {
        "Id": 47,
        "TimeZone": "Central Daylight TimeCDST – Central Daylight Saving TimeNACDT – North American Central Daylight TimeHAC – Heure Avancée du Centre (French)",
        "Abbreviation": "CDT",
        "Location": "North America",
        "Offset": "UTC -5"
    },
    {
        "Id": 62,
        "TimeZone": "Central Standard TimeCT – Central TimeNACST – North American Central Standard TimeCST – Tiempo Central Estándar (Spanish)HNC – Heure Normale du Centre (French)",
        "Abbreviation": "CST",
        "Location": "North AmericaCentral America",
        "Offset": "UTC -6"
    },
    {
        "Id": 65,
        "TimeZone": "Central Time",
        "Abbreviation": "CT",
        "Location": "North America",
        "Offset": "UTC -6:00 / -5:00"
    },
    {
        "Id": 77,
        "TimeZone": "Eastern Daylight TimeEDST – Eastern Daylight Savings TimeNAEDT – North American Eastern Daylight TimeHAE – Heure Avancée de l'Est  (French)EDT – Tiempo de verano del Este (Spanish)",
        "Abbreviation": "EDT",
        "Location": "North AmericaCaribbean",
        "Offset": "UTC -4"
    },
    {
        "Id": 80,
        "TimeZone": "Eastern Greenland Summer TimeEGST – East Greenland Summer Time",
        "Abbreviation": "EGST",
        "Location": "North America",
        "Offset": "UTC +0"
    },
    {
        "Id": 81,
        "TimeZone": "East Greenland TimeEGT – Eastern Greenland Time",
        "Abbreviation": "EGT",
        "Location": "North America",
        "Offset": "UTC -1"
    },
    {
        "Id": 82,
        "TimeZone": "Eastern Standard TimeET – Eastern TimeNAEST – North American Eastern Standard TimeET – Tiempo del Este  (Spanish)HNE – Heure Normale de l'Est (French)",
        "Abbreviation": "EST",
        "Location": "North AmericaCaribbeanCentral America",
        "Offset": "UTC -5"
    },
    {
        "Id": 83,
        "TimeZone": "Eastern Time",
        "Abbreviation": "ET",
        "Location": "North AmericaCaribbean",
        "Offset": "UTC -5:00 / -4:00"
    },
    {
        "Id": 97,
        "TimeZone": "Greenwich Mean TimeUTC – Coordinated Universal TimeGT – Greenwich Time",
        "Abbreviation": "GMT",
        "Location": "EuropeAfricaNorth AmericaAntarctica",
        "Offset": "UTC +0"
    },
    {
        "Id": 102,
        "TimeZone": "Hawaii-Aleutian Daylight TimeHADT – Hawaii Daylight Time",
        "Abbreviation": "HDT",
        "Location": "North America",
        "Offset": "UTC -9"
    },
    {
        "Id": 106,
        "TimeZone": "Hawaii Standard TimeHAST – Hawaii-Aleutian Standard Time",
        "Abbreviation": "HST",
        "Location": "North AmericaPacific",
        "Offset": "UTC -10"
    },
    {
        "Id": 135,
        "TimeZone": "Mountain Daylight TimeMDST – Mountain Daylight Saving TimeNAMDT – North American Mountain Daylight TimeHAR – Heure Avancée des Rocheuses (French)",
        "Abbreviation": "MDT",
        "Location": "North America",
        "Offset": "UTC -6"
    },
    {
        "Id": 140,
        "TimeZone": "Mountain Standard TimeMT – Mountain TimeNAMST – North American Mountain Standard TimeHNR – Heure Normale des Rocheuses (French)",
        "Abbreviation": "MST",
        "Location": "North America",
        "Offset": "UTC -7"
    },
    {
        "Id": 141,
        "TimeZone": "Mountain Time",
        "Abbreviation": "MT",
        "Location": "North America",
        "Offset": "UTC -7:00 / -6:00"
    },
    {
        "Id": 147,
        "TimeZone": "Newfoundland Daylight TimeHAT – Heure Avancée de Terre-Neuve (French)",
        "Abbreviation": "NDT",
        "Location": "North America",
        "Offset": "UTC -2:30"
    },
    {
        "Id": 154,
        "TimeZone": "Newfoundland Standard TimeHNT – Heure Normale de Terre-Neuve (French)",
        "Abbreviation": "NST",
        "Location": "North America",
        "Offset": "UTC -3:30"
    },
    {
        "Id": 163,
        "TimeZone": "Pacific Daylight TimePDST – Pacific Daylight Saving TimeNAPDT – North American Pacific Daylight TimeHAP – Heure Avancée du Pacifique (French)",
        "Abbreviation": "PDT",
        "Location": "North America",
        "Offset": "UTC -7"
    },
    {
        "Id": 171,
        "TimeZone": "Pierre & Miquelon Daylight Time",
        "Abbreviation": "PMDT",
        "Location": "North America",
        "Offset": "UTC -2"
    },
    {
        "Id": 172,
        "TimeZone": "Pierre & Miquelon Standard Time",
        "Abbreviation": "PMST",
        "Location": "North America",
        "Offset": "UTC -3"
    },
    {
        "Id": 174,
        "TimeZone": "Pacific Standard TimePT – Pacific TimeNAPST – North American Pacific Standard TimePT – Tiempo del Pacífico (Spanish)HNP – Heure Normale du Pacifique (French)",
        "Abbreviation": "PST",
        "Location": "North America",
        "Offset": "UTC -8"
    },
    {
        "Id": 176,
        "TimeZone": "Pacific Time",
        "Abbreviation": "PT",
        "Location": "North America",
        "Offset": "UTC -8:00 / -7:00"
    },
    {
        "Id": 229,
        "TimeZone": "Western Greenland Summer TimeWGST – West Greenland Summer Time",
        "Abbreviation": "WGST",
        "Location": "North America",
        "Offset": "UTC -2"
    },
    {
        "Id": 230,
        "TimeZone": "West Greenland TimeWGT – Western Greenland Time",
        "Abbreviation": "WGT",
        "Location": "North America",
        "Offset": "UTC -3"
    }
]
                                                                                                                                                                                                                    
                                                                                                    

Time zone by location - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/3949/global+time+locator+api/4698/time+zone+by+location?location=North America' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Global Time Locator API REST API, simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.

🚀 Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • ✔︎ Only Pay for Successful Requests
  • ✔︎ Free 7-Day Trial
  • ✔︎ Multi-Language Support
  • ✔︎ One API Key, All APIs.
  • ✔︎ Intuitive Dashboard
  • ✔︎ Comprehensive Error Handling
  • ✔︎ Developer-Friendly Docs
  • ✔︎ Postman Integration
  • ✔︎ Secure HTTPS Connections
  • ✔︎ Reliable Uptime

Global Time Locator API FAQs

To use this API you can use the endpoint all times zones or use time zone by location to get times zone by location.

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.

The Global Time Locator API designed to provide accurate and up-to-date time zone information for locations around the world. It allows users to retrieve accurate time zone data from their location.

The "GET All Time Zones" endpoint returns a list of all available time zones, including their unique identifiers, names, abbreviations, locations, and UTC offsets. The "GET Time Zone by Location" endpoint provides similar data but filtered based on the specified location parameter.

Key fields in the response data include "Id" (unique identifier), "TimeZone" (name of the time zone), "Abbreviation" (short form), "Location" (geographic area), and "Offset" (UTC time difference).

The response data is organized in JSON format, structured as an array of objects. Each object represents a time zone with its associated fields, making it easy to parse and utilize in applications.

The "GET All Time Zones" endpoint provides comprehensive time zone data globally, while the "GET Time Zone by Location" endpoint offers specific time zone details based on user-defined locations, enhancing localization in applications.

The "GET Time Zone by Location" endpoint requires a location parameter, which can be a city name, country code, or geographic coordinates. This allows users to customize their requests for specific time zone information.

Data accuracy is maintained through regular updates and quality checks against reliable time zone databases. This ensures that users receive the most current and precise time zone information for their applications.

Typical use cases include scheduling international meetings, displaying local times for travel platforms, and ensuring accurate time conversions in finance applications, all of which rely on precise time zone data.

Users can utilize the returned data by integrating it into their applications to display accurate local times, perform time zone conversions, and enhance user experience through automatic time zone detection based on location.

General FAQs

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.


Related APIs