Worldwide Earthquakes API GET

Documentation Start for free →

Earthquake is a simple tool for getting earthquake data. It returns the earthquake data for the past hour.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/earthquake

Verification

Format

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

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Worldwide Earthquakes response payload
  }
}

About the Worldwide Earthquakes API

Earthquake works by analyzing the earthquake data provided and returning the earthquake data for the past hour. It uses various sources to determine the earthquake data and returns the data.

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 Worldwide Earthquakes

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 Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the Worldwide Earthquakes API.

Read the docs →

What does the Worldwide Earthquakes API do?

Earthquake is a simple tool for getting earthquake data. It returns the earthquake data for the past hour.

How do I authenticate Worldwide Earthquakes 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 Worldwide Earthquakes 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 Worldwide Earthquakes 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 Worldwide Earthquakes 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 Worldwide Earthquakes API use?

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

Request parameters — GET /v1/earthquake

This endpoint takes no parameters

Call it with your key and nothing else. Any query string you send is ignored rather than rejected.

Example request

1
2

curl "https://api.apiverve.com/v1/earthquake" \
  -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/earthquake

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": {
    "earthquakes_LastUpdated": "2026-02-18T12:00:00.000Z",
    "earthquakes_LastHour": 9,
    "count24h": 187,
    "largestMagnitude24h": 5.2,
    "avgMagnitude24h": 1.84,
    "earthquakes": [
      {
        "mag": 3.4,
        "place": "153 km SSW of Channel Islands Beach, California",
        "time": 1765921110756,
        "felt": 1,
        "cdi": 2.2,
        "mmi": 2.538,
        "status": "reviewed",
        "tsunami": 0,
        "sig": 178,
        "net": "us",
        "types": ",dyfi,nearby-cities,origin,phase-data,scitech-link,shakemap,",
        "nst": 36,
        "dmin": 0.479,
        "rms": 0.65,
        "gap": 247,
        "magType": "ml",
        "type": "earthquake",
        "title": "M 3.4 - 153 km SSW of Channel Islands Beach, California",
        "coordinates": [
          -119.931,
          32.9103
        ]
      },
      {
        "mag": 2.25,
        "place": "6 km NW of The Geysers, CA",
        "time": 1765921522850,
        "status": "automatic",
        "tsunami": 0,
        "sig": 78,
        "net": "nc",
        "types": ",focal-mechanism,nearby-cities,origin,phase-data,",
        "nst": 54,
        "dmin": 0.01126,
        "rms": 0.05,
        "gap": 23,
        "magType": "md",
        "type": "earthquake",
        "title": "M 2.3 - 6 km NW of The Geysers, CA",
        "coordinates": [
          -122.792831,
          38.819332
        ]
      }
    ]
  }
}

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
`earthquakes_LastUpdated`	string	`"2026-02-18T12:00:00.000Z"`	Timestamp of when the underlying earthquake data was last refreshed from USGS
`earthquakes_LastHour`	number	`9`	Number of earthquakes recorded in the past hour
`count24h`	number	`187`	Total earthquake count in the past 24 hours
`largestMagnitude24h`	number	`5.2`	Largest earthquake magnitude recorded in the past 24 hours
`avgMagnitude24h`Premium	number	`1.84`	Average earthquake magnitude across the past 24 hours
`earthquakes`	array[2]		Earthquakes recorded in the past hour
`mag`	number	`3.4`	Magnitude of the earthquake
`place`	string	`"153 km SSW of Channel Islands Beach, California"`	Human-readable description of the epicenter's location
`time`	number	`1765921110756`	Unix timestamp, in milliseconds, of when the earthquake occurred
`felt`	number	`1`	Number of 'felt' reports submitted by the public for this event; absent when none were submitted
`cdi`	number	`2.2`	Maximum reported intensity of the event from citizen 'Did You Feel It?' reports
`mmi`	number	`2.538`	Maximum estimated instrumental intensity of the event
`status`	string	`"reviewed"`	Review status of the event: 'automatic' if produced by an automatic system, 'reviewed' if a human seismologist verified it
`tsunami`	number	`0`	Whether a tsunami warning was associated with this event (1) or not (0)
`sig`	number	`178`	A number describing how significant the event is, based on magnitude, felt reports, and other factors; larger numbers indicate a more significant event
`net`	string	`"us"`	ID of the seismic network that originally authored the event
`types`	string	`",dyfi,nearby-cities,origin,phase-data,scitech-link,shakemap,"`	Comma-separated list of product types associated with this event
`nst`	number	`36`	Number of seismic stations used to determine the earthquake's location
`dmin`	number	`0.479`	Horizontal distance, in degrees, from the epicenter to the nearest reporting station
`rms`	number	`0.65`	Root-mean-square travel time residual of the seismic stations used to locate the event, in seconds
`gap`	number	`247`	Largest azimuthal gap, in degrees, between adjacent reporting stations
`magType`	string	`"ml"`	Method or algorithm used to calculate the reported magnitude
`type`	string	`"earthquake"`	Type of seismic event, e.g. earthquake or quarry blast
`title`	string	`"M 3.4 - 153 km SSW of Channel Islands Beach, California"`	Formatted summary combining the magnitude and place, e.g. 'M 2.5 - 3 km ESE of Camarillo, CA'
`coordinates`	array	`[-119.931, ...]`	Epicenter location as [longitude, latitude]

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	Worldwide Earthquakes 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/earthquake

No SDK to install — this is a plain HTTPS call to /v1/earthquake 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/earthquake" \
  -H "x-api-key: YOUR_API_KEY"

Resources

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

Also published for

@apiverve/earthquakenpm APIVerve.API.WorldwideEarthquakesNuGet

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/earthquake

Install the Node.js SDK, then call the Worldwide Earthquakes 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/earthquake

Node.js

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

Resources

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

Also published for

APIVerve.API.WorldwideEarthquakesNuGet

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

Call it from Python — GET /v1/earthquake

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

Python

import requests

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

Resources

Also published for

@apiverve/earthquakenpm APIVerve.API.WorldwideEarthquakesNuGet

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/earthquake

Install the C# / .NET SDK, then call the Worldwide Earthquakes 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.WorldwideEarthquakes

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/earthquake");
Console.WriteLine(json);

Resources

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

Also published for

@apiverve/earthquakenpm

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

Call it from Go — GET /v1/earthquake

No SDK to install — this is a plain HTTPS call to /v1/earthquake 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/earthquake", 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/earthquakenpm APIVerve.API.WorldwideEarthquakesNuGet

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

Call it from PHP — GET /v1/earthquake

No SDK to install — this is a plain HTTPS call to /v1/earthquake 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/earthquake");
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/earthquakenpm APIVerve.API.WorldwideEarthquakesNuGet

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

Call it from Ruby — GET /v1/earthquake

No SDK to install — this is a plain HTTPS call to /v1/earthquake 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/earthquake")
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/earthquakenpm APIVerve.API.WorldwideEarthquakesNuGet

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

All articles →

Building Health-Conscious Apps With Air Quality DataAir quality affects millions of users. Here's how to integrate environmental health data meaningfully.Read

API Caching: The Cheapest Performance WinEvery duplicate API call is wasted money. Here's how to cache responses properly—and when not to.Read

Weather APIs: Build a Dashboard That's Actually UsefulCurrent conditions, forecasts, air quality, sunrise times—here's how to build a weather dashboard users will love.Read

Worldwide Earthquakes API GET

Try it — live request, no key required

About the Worldwide Earthquakes API

Ways to call it

Other ways to use Worldwide Earthquakes

Questions.

Request parameters — GET /v1/earthquake

Authentication

Response — GET /v1/earthquake

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/earthquake

Resources

Also published for

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

Resources

Also published for

Call it from Python — GET /v1/earthquake

Resources

Also published for

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

Resources

Also published for

Call it from Go — GET /v1/earthquake

Resources

Also published for

Call it from PHP — GET /v1/earthquake

Resources

Also published for

Call it from Ruby — GET /v1/earthquake

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Worldwide Earthquakes API

Weather

Related articles

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

Explore the catalog