Historical Events API GET

Historical Events is a simple tool for getting historical events. It returns a list of historical events between 300BC and 2012

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/historicalevents

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Historical Events response payload
  }
}

About the Historical Events API

Historical Events works by retrieving historical events from various reliable sources and curated lists of events. It them parses and provides them in a structured format. Super useful for history buffs and trivia enthusiasts.

What people use it for

History Buffs: Get historical events by using the Historical Events API. Explore historical events from different time periods and regions to learn more about the past
Trivia Games: Create trivia games by using the Historical Events API to get historical events. Use the data to generate questions and answers for history-themed games
Educational Purposes: Use the Historical Events API for educational purposes to teach students about historical events. Provide students with a list of historical events to study and discuss
Research Projects: Gather historical data for research projects by using the Historical Events API. Use the data to analyze trends, patterns, and events from different time periods

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use Historical Events

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the Historical Events API.

Read the docs →

What does the Historical Events API do?

Historical Events is a simple tool for getting historical events. It returns a list of historical events between 300BC and 2012

How do I authenticate Historical Events API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Historical Events API cost?

Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Historical Events API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Historical Events API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Historical Events API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — GET /v1/historicalevents

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`text`Required	string	`moon landing`	The keyword for which you want to get the historical events (e.g., moon landing)

Example request

1
2

curl "https://api.apiverve.com/v1/historicalevents?text=moon%20landing" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — GET /v1/historicalevents

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "count": 6,
    "filteredOn": [
      "text"
    ],
    "events": [
      {
        "year": "1969",
        "month": "05",
        "day": "18",
        "date": "1969/05/18",
        "event": " Apollo program: ''Apollo 10'' (Tom Stafford, Gene Cernan, John Young) is launched, on the full dress-rehearsal for the Moon landing.",
        "range": "May",
        "granularity": "year"
      },
      {
        "year": "1969",
        "month": "05",
        "day": "25",
        "date": "1969/05/25",
        "event": "Apollo program: ''Apollo 10'' returns to Earth, after a successful 8-day test of all the components needed for the upcoming first manned Moon landing.",
        "range": "May",
        "granularity": "year"
      },
      {
        "year": "1969",
        "month": "07",
        "day": "20",
        "date": "1969/07/20",
        "event": " Apollo program: The lunar module ''Eagle'' lands on the lunar surface. An estimated 500 million people worldwide watch in awe as Neil Armstrong takes his historic first steps on the Moon at 02:56 UTC, the largest television audience for a live broadcast at that time.cite web|title=Manned Space Chronology: Apollo_11|url=<a href=\"http://www.spaceline.org/flightchron/apollo11.html|publisher=spaceline.org|accessdate=2008-02-06|\">http://www.spaceline.org/flightchron/apollo11.html|publisher=spaceline.org|accessdate=2008-02-06|</a>; archiveurl= <a href=\"http://web.archive.org/web/20080214213826/http://www.spaceline.org/flightchron/apollo11.html|\">http://web.archive.org/web/20080214213826/http://www.spaceline.org/flightchron/apollo11.html|</a>; archivedate= 14 February 2008 !--DASHBot--| deadurl= no}}cite web|title= Apollo Anniversary: Moon Landing quotInspired Worldquot|url=<a href=\"http://news.nationalgeographic.com/news/2004/07/0714_040714_moonlanding.html|publisher=nationalgeographic.com|accessdate=2008-02-06|\">http://news.nationalgeographic.com/news/2004/07/0714_040714_moonlanding.html|publisher=nationalgeographic.com|accessdate=2008-02-06|</a>; archiveurl= <a href=\"http://web.archive.org/web/20080209140059/http://news.nationalgeographic.com/news/2004/07/0714_040714_moonlanding.html|\">http://web.archive.org/web/20080209140059/http://news.nationalgeographic.com/news/2004/07/0714_040714_moonlanding.html|</a>; archivedate= 9 February 2008 !--DASHBot--| deadurl= no}}",
        "range": "July",
        "granularity": "year"
      },
      {
        "year": "1969",
        "month": "07",
        "day": "20",
        "date": "1969/07/20",
        "event": "The ''Apollo 11'' astronauts return from the first successful Moon landing, and are placed in biological isolation for several days, on the chance they may have brought back lunar germs. The airless lunar environment is later determined to preclude microscopic life.",
        "range": "July",
        "granularity": "year"
      },
      {
        "year": "1971",
        "month": "02",
        "day": "08",
        "date": "1971/02/08",
        "event": "Apollo program: ''Apollo 14'' returns to Earth after the third manned Moon landing.",
        "range": "February",
        "granularity": "year"
      },
      {
        "year": "1973",
        "month": "01",
        "day": "07",
        "date": "1973/01/07",
        "event": "Elvis Presley's concert in Hawaii. The first worldwide telecast by an entertainer watched by more people than watched the Apollo moon landings.",
        "range": "January",
        "granularity": "year"
      }
    ]
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`count`	number	`6`	Total number of historical events returned in results
`filteredOn`Premium	array	`[text]`	Array of filter criteria applied to generate results
`events`	array[6]		Array of historical event objects matching search criteria
`year`Premium	string	`"1969"`	Calendar year when the historical event occurred
`month`Premium	string	`"05"`	Month number (01-12) when the event occurred
`day`Premium	string	`"18"`	Day of month when the historical event occurred
`date`Premium	string	`"1969/05/18"`	Full date in YYYY/MM/DD format for the event
`event`	string	`" Apollo program: ''Apollo 10'' (Tom Stafford, Gene Cernan, John Young) is launched, on the full dress-rehearsal for the Moon landing."`	Detailed description and text of the historical event
`range`Premium	string	`"May"`	Named month range or period when the event occurred
`granularity`Premium	string	`"year"`	Precision level of date (year, month, or specific day)

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	Historical Events calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/historicalevents

No SDK to install — this is a plain HTTPS call to /v1/historicalevents with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/historicalevents" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/historicalevents-apiSource, issues and the examples this page is built from.ReferenceHistorical Events API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/historicaleventsnpm apiverve-historicaleventsPyPI APIVerve.API.HistoricalEventsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/historicalevents

Install the Node.js SDK, then call the Historical Events API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/historicalevents

Node.js

const res = await fetch("https://api.apiverve.com/v1/historicalevents", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/historicaleventsThe published Node.js client, versioned and signed.GitHubapiverve/historicalevents-apiSource, issues and the examples this page is built from.ReferenceHistorical Events API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

apiverve-historicaleventsPyPI APIVerve.API.HistoricalEventsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/historicalevents

Install the Python SDK, then call the Historical Events API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — PyPI

pip install apiverve-historicalevents

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/historicalevents",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

PyPIapiverve-historicaleventsThe published Python client, versioned and signed.GitHubapiverve/historicalevents-apiSource, issues and the examples this page is built from.ReferenceHistorical Events API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/historicaleventsnpm APIVerve.API.HistoricalEventsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/historicalevents

Install the C# / .NET SDK, then call the Historical Events API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.HistoricalEvents

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/historicalevents");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.HistoricalEventsThe published C# / .NET client, versioned and signed.GitHubapiverve/historicalevents-apiSource, issues and the examples this page is built from.ReferenceHistorical Events API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/historicaleventsnpm apiverve-historicaleventsPyPI

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/historicalevents

No SDK to install — this is a plain HTTPS call to /v1/historicalevents with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/historicalevents", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/historicaleventsnpm apiverve-historicaleventsPyPI APIVerve.API.HistoricalEventsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/historicalevents

No SDK to install — this is a plain HTTPS call to /v1/historicalevents with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/historicalevents");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/historicaleventsnpm apiverve-historicaleventsPyPI APIVerve.API.HistoricalEventsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/historicalevents

No SDK to install — this is a plain HTTPS call to /v1/historicalevents with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/historicalevents")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/historicaleventsnpm apiverve-historicaleventsPyPI APIVerve.API.HistoricalEventsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

Python API Tutorial: Your First APIVerve Call10 lines of Python. That's all it takes to call 300+ APIs. Here's the complete quickstart for Python developers.Read

REST vs GraphQL: Which Should You Use?Skip the theory. Here's when to use REST endpoints and when GraphQL actually makes sense.Read

Complete Guide to API Testing with PostmanMaster API testing with Postman. Learn collections, environments, automated tests, and debugging techniques.Read

Historical Events API GET

Try it — live request, no key required

About the Historical Events API

What people use it for

Ways to call it

Other ways to use Historical Events

Questions.

Request parameters — GET /v1/historicalevents

Required

Authentication

Response — GET /v1/historicalevents

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/historicalevents

Resources

Also published for

Call it from Node.js — GET /v1/historicalevents

Resources

Also published for

Call it from Python — GET /v1/historicalevents

Resources

Also published for

Call it from C# / .NET — GET /v1/historicalevents

Resources

Also published for

Call it from Go — GET /v1/historicalevents

Resources

Also published for

Call it from PHP — GET /v1/historicalevents

Resources

Also published for

Call it from Ruby — GET /v1/historicalevents

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Historical Events API

Entertainment

Related articles

Ready to build with Historical Events? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog