Returns a list of up to 10 events that match the search parameters.
Educational Timeline Integration:
Interactive Museum Exhibits:
Historical Research and Analysis:
Content Enrichment for Media Productions:
Travel Planning with Historical Context:
Besides API call limitations per month, there is no other limitation.
Returns a list of up to 10 events that match the search parameters.
At least one of the following parameters is required: text
, year
, month
, day
.
text
(optional) - query text to search events by. Use keywords or short phrases for best-match results.
year
(optional) - 4-digit year (e.g. 1776
). For BC/BCE years, use a negative integer (e.g. -351
for 351 BC).
month
(optional) - integer month (e.g. 3
for March).
day
(optional) - calendar day of the month.
offset
(optional) - number of results to offset (for pagination).
Get Events - Endpoint Features
Object | Description |
---|
[{"year": "-45", "month": "01", "day": "01", "event": "The Julian calendar takes effect as the civil calendar of the Roman Empire, establishing January 1 as the new date of the new year."}, {"year": "366", "month": "01", "day": "02", "event": "The Alemanni cross the frozen Rhine in large numbers, invading the Roman Empire."}, {"year": "250", "month": "01", "day": "03", "event": "Emperor Decius orders everyone in the Roman Empire (except Jews) to make sacrifices to the Roman gods."}, {"year": "-27", "month": "01", "day": "16", "event": "Gaius Julius Caesar Octavianus is granted the title Augustus by the Roman Senate, marking the beginning of the Roman Empire."}, {"year": "379", "month": "01", "day": "19", "event": "Emperor Gratian elevates Flavius Theodosius at Sirmium to Augustus, and gives him authority over all the eastern provinces of the Roman Empire."}, {"year": "1719", "month": "01", "day": "23", "event": "The Principality of Liechtenstein is created within the Holy Roman Empire."}, {"year": "98", "month": "01", "day": "27", "event": "Trajan succeeds his adoptive father Nerva as Roman emperor; under his rule the Roman Empire will reach its maximum extent."}, {"year": "1018", "month": "01", "day": "30", "event": "Poland and the Holy Roman Empire conclude the Peace of Bautzen."}, {"year": "421", "month": "02", "day": "08", "event": "Constantius III becomes co-Emperor of the Western Roman Empire."}, {"year": "55", "month": "02", "day": "11", "event": "The death under mysterious circumstances of Tiberius Claudius Caesar Britannicus, heir to the Roman empire, on the eve of his coming of age clears the way for Nero to become Emperor."}]
curl --location --request GET 'https://zylalabs.com/api/3207/events+in+history+api/3430/get+events' --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 Events in History API is regularly updated to include new historical events and ensure accuracy. Updates occur on a scheduled basis, typically monthly, incorporating the latest historical research and discoveries.
Absolutely. The API supports advanced queries, allowing users to filter events based on specific time periods, geographical regions, or a combination of both. This feature ensures a targeted and customized exploration of historical data.
Yes, the Events in History API includes categorization by themes or topics. Users can explore events based on predefined categories such as wars, cultural movements, scientific breakthroughs, and more, enabling focused research and analysis.
Currently, the API does not support external contributions. However, we value user feedback. If you identify discrepancies or have suggestions for new events, please reach out to our support team, and we will consider them for future updates.
The API normalizes historical dates into a standardized format to ensure consistency across different calendars. Users can specify date ranges using universally accepted formats or utilize the API's conversion capabilities for seamless historical research.
The API returns a list of historical events, each containing details such as the year, month, day, and a description of the event. This allows users to explore significant moments in history across various time periods.
Each event in the response includes the fields: "year," "month," "day," and "event." These fields provide a structured overview of the event's date and its significance, facilitating easy understanding and analysis.
The response data is organized as a JSON array, where each object represents a historical event. Each object contains specific fields for year, month, day, and event description, making it straightforward to parse and utilize.
Users can customize their requests using parameters such as "text" (for keyword searches), "year," "month," "day," and "offset" (for pagination). At least one of the first four parameters is required for a successful query.
The API provides information on a wide range of historical events, including political milestones, cultural achievements, scientific discoveries, and conflicts. This diverse coverage allows for comprehensive exploration of human history.
Users can leverage the returned data to create educational content, enhance research projects, or develop interactive applications. By analyzing the event descriptions and dates, users can draw connections between historical occurrences and their impacts.
The data is compiled from reputable historical records, academic research, and verified sources to ensure accuracy. This rigorous sourcing process helps maintain the integrity of the information provided through the API.
Data accuracy is maintained through regular updates and quality checks, which involve cross-referencing historical events with trusted sources. This process ensures that the information remains reliable and up-to-date for users.
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:
501ms
Service Level:
100%
Response Time:
616ms
Service Level:
100%
Response Time:
3,051ms
Service Level:
100%
Response Time:
172ms
Service Level:
100%
Response Time:
2,231ms
Service Level:
100%
Response Time:
1,114ms
Service Level:
100%
Response Time:
448ms
Service Level:
100%
Response Time:
296ms
Service Level:
100%
Response Time:
335ms
Service Level:
100%
Response Time:
750ms
Service Level:
100%
Response Time:
3,976ms
Service Level:
100%
Response Time:
2,125ms
Service Level:
100%
Response Time:
621ms
Service Level:
100%
Response Time:
2,553ms
Service Level:
100%
Response Time:
729ms
Service Level:
100%
Response Time:
1,160ms
Service Level:
100%
Response Time:
397ms
Service Level:
100%
Response Time:
3,064ms
Service Level:
100%
Response Time:
847ms
Service Level:
100%
Response Time:
696ms