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.
Service Level:
100%
Response Time:
1,158ms
Service Level:
100%
Response Time:
521ms
Service Level:
100%
Response Time:
1,158ms
Service Level:
100%
Response Time:
1,158ms
Service Level:
100%
Response Time:
627ms
Service Level:
100%
Response Time:
1,158ms
Service Level:
100%
Response Time:
1,158ms
Service Level:
100%
Response Time:
523ms
Service Level:
100%
Response Time:
1,158ms
Service Level:
100%
Response Time:
1,444ms
Service Level:
100%
Response Time:
204ms
Service Level:
100%
Response Time:
1,049ms
Service Level:
100%
Response Time:
552ms
Service Level:
100%
Response Time:
139ms
Service Level:
100%
Response Time:
605ms
Service Level:
100%
Response Time:
186ms
Service Level:
100%
Response Time:
147ms
Service Level:
100%
Response Time:
458ms
Service Level:
100%
Response Time:
12,980ms
Service Level:
100%
Response Time:
962ms