Meteorite Landings API Reference

Overview

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.

Endpoint

One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.

GEThttps://api.apiverve.com/v1/meteorites

curl "https://api.apiverve.com/v1/meteorites?name=Allende&mass=100&year=1969" \
  -H "x-api-key: your_api_key_here"

const res = await fetch('https://api.apiverve.com/v1/meteorites?name=Allende&mass=100&year=1969', {
  headers: { 'x-api-key': 'your_api_key_here' },
});

if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);

const { data } = await res.json();
console.log(data);

import requests

res = requests.get(
    "https://api.apiverve.com/v1/meteorites?name=Allende&mass=100&year=1969",
    headers={"x-api-key": "your_api_key_here"},
    timeout=15,
)
res.raise_for_status()

print(res.json()["data"])

package main

import (
	"fmt"
	"io"
	"net/http"
)

func main() {
	req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/meteorites?name=Allende&mass=100&year=1969", nil)
	req.Header.Set("x-api-key", "your_api_key_here")

	res, err := http.DefaultClient.Do(req)
	if err != nil {
		panic(err)
	}
	defer res.Body.Close()

	out, _ := io.ReadAll(res.Body)
	fmt.Println(string(out))
}

Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.

Authentication

Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.

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.

Parameters

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.

Parameter	Type	Description
`name`Required	string	The name of the meteorite you want to search for
`mass`Optional	number	Minimum mass of the meteorite in grams
`year`OptionalPremium	number	The year the meteorite fell to Earth

Response

Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.

Sample response

{
  "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
`geolocation`Premium	object	`{...}`	GeoJSON object with landing site coordinates
`type`Premium	string	`"Point"`
`coordinates`Premium	array	`[-105.31667, ...]`

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted	A key restriction or IP allow-list; see key scoping.
`429`	Rate limited, or out of credits	Read `error` to tell them apart; see rate limits.

Use cases

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

Other ways to use Meteorite Landings

Set up Meteorite Landings on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →

Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →

Meteorite Landings