Meteorites is a simple tool for getting meteorite data. It returns a list of meteorites that have fallen to Earth.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Meteorite Landings response payload
}
}
About the Meteorite Landings API
Meteorites works by retrieving meteorite data from various reliable sources and providing it in a structured format. You can expect accurate and up-to-date information.
What people use it for
- Astronomy Research
- Create Research platforms by using the Meteorites API to get meteorite data. Use the data to study meteorite landings and their impact on Earth
- Geology Studies
- Provide Geology studies by using the Meteorites API to get meteorite data. Use the data to analyze meteorite compositions and structures
- Space Exploration
- Explore meteorite landings by using the Meteorites API to learn about extraterrestrial objects. Use the data to discover more about the solar system and beyond
- Historical Analysis
- Analyze meteorite data by using the Meteorites API to investigate historical meteorite landings. Use the data to learn about significant events and impacts on Earth
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
Other ways to use Meteorite Landings
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Meteorite Landings API do?
How do I authenticate Meteorite Landings API requests?
How much does the Meteorite Landings API cost?
How fast is the Meteorite Landings API?
What response formats does the Meteorite Landings API support?
What HTTP method does the Meteorite Landings API use?
Request parameters — GET /v1/meteorites
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 |
|---|---|---|---|
nameRequired | string | Allende | The name of the meteorite you want to search for |
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
massOptional | number | 100 | Minimum mass of the meteorite in grams |
yearOptionalPremium | number | 1969 | The year the meteorite fell to Earth |
curl "https://api.apiverve.com/v1/meteorites?name=Allende&mass=100&year=1969" \
-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-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
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/meteorites
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.
{
"status": "ok",
"error": null,
"data": {
"count": 1,
"filteredOn": [
"name"
],
"meteors": [
{
"name": "Allende",
"recclass": "CV3",
"mass": "2000000",
"year": "1969",
"geolocation": {
"type": "Point",
"coordinates": [
-105.31667,
26.96667
]
}
}
]
}
}
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 | 1 | Total number of meteorites matching the search criteria |
filteredOn | array | [name] | Array of field names used to filter the meteorite results |
meteors | array[1] | Array of meteorite objects matching the search query | |
name | string | "Allende" | Official name of the meteorite specimen |
recclass | string | "CV3" | Meteorite classification code (composition and type) |
mass | string | "2000000" | Mass of the meteorite in grams as string |
year | string | "1969" | Year the meteorite fell to Earth as string |
geolocationPremium | object | {...} | GeoJSON object with landing site coordinates |
typePremium | string | "Point" | |
coordinatesPremium | array | [-105.31667, ...] |
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 cycle's allowance |
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 | Meteorite Landings 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.
Call it from cURL — GET /v1/meteorites
No SDK to install — this is a plain HTTPS call to /v1/meteorites with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/meteorites" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
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/meteorites
Install the Node.js SDK, then call the Meteorite Landings API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/meteoritesconst res = await fetch("https://api.apiverve.com/v1/meteorites", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/meteorites
No SDK to install — this is a plain HTTPS call to /v1/meteorites with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/meteorites",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
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/meteorites
Install the C# / .NET SDK, then call the Meteorite Landings API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.MeteoriteLandingsusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/meteorites");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/meteorites
No SDK to install — this is a plain HTTPS call to /v1/meteorites 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/meteorites", 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
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/meteorites
No SDK to install — this is a plain HTTPS call to /v1/meteorites with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/meteorites");
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
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/meteorites
No SDK to install — this is a plain HTTPS call to /v1/meteorites with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/meteorites")
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.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Meteorite Landings form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Meteorite Landings API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog.
Science
- Julian Day Calculator
- Meteorite Landings
- Periodic Table
- Stars Lookup
Related articles
All articles →
Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read
Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read
Business Day Math Is Harder Than You ThinkWeekends, holidays, and country-specific rules make working day calculations surprisingly tricky. Here's what to watch for.Read