Global Temporal Data API

Global Temporal Data API

The Global Temporal Data API provides accurate time zone information with historical data for seamless integration of global applications.

API description

About the API:  

The Global Temporal Data API is a robust and indispensable tool for developers looking to integrate accurate and up-to-date time zone information into their applications, websites or services. In a globally connected digital landscape, where real-time interactions span different regions, having accurate time zone data is crucial for everything from scheduling events to coordinating international communications.

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

One of the key features of the Global Temporal Data API is its ability to retrieve the current time for specific locations. Users can query the API for the current time in any time zone, allowing them to present users with accurate and synchronized time information based on their geographic preferences.

In addition, the Global Temporal Data API makes it easy to convert between different time zones. Developers can seamlessly convert timestamps from one time zone to another, ensuring consistency of time-related data across global applications. This functionality is crucial for business, finance and any industry where time accuracy and timing are essential.

Developers can also leverage the Global Temporal Data API to implement features such as automatic time zone detection. By determining a user's geographic location through their IP address or other means, applications can dynamically adjust the displayed time zone, providing a seamless and personalized user experience.

In conclusion, the Global Temporal Data API is an essential tool for users facing the challenges of global time management in their applications. This API allows users to create applications that seamlessly manage time-related information in different 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/3002/global+temporal+data+api/3163/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/3002/global+temporal+data+api/3163/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/3002/global+temporal+data+api/3165/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/3002/global+temporal+data+api/3165/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 Temporal Data 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
  • Dedicated account manager
  • Service-level agreement (SLA)

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

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.

Sure, you can use it and pay only when you use it. The credit can’t be expired.

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 Temporal Data API is a comprehensive tool designed to provide developers with accurate and up-to-date information related to time zones across the world.

Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.

Prices are listed in USD. 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 with paying by card, just contact us at [email protected]

Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further

Prices are based on a recurring monthly subscription depending on the plan selected — plus overage fees applied when a developer exceeds a plan’s quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.

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.

Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.

Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.

You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]

 Service Level
100%
 Response Time
87ms

Category:


Tags:


Related APIs