Meteorite Landings API
Overview
To use Meteorite Landings, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/meteoritesExample
How to call the Meteorite Landings API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/meteorites?name=Allende&mass=100&year=1969" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/meteorites?name=Allende&mass=100&year=1969', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/meteorites?name=Allende&mass=100&year=1969', headers=headers)
data = response.json()
print(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")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"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
]
}
}
]
}
}Authentication
The Meteorite Landings API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Meteorite Landings API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Meteorite Landings API:
Get Meteorites
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
name | string | required | The name of the meteorite you want to search for | - | |
mass | number | optional | Minimum mass of the meteorite in grams | - | |
yearPremium | number | optional | The year the meteorite fell to Earth | - |
Response
The Meteorite Landings API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<count>1</count>
<filteredOn>
<item>name</item>
</filteredOn>
<meteors>
<meteor>
<name>Allende</name>
<recclass>CV3</recclass>
<mass>2000000</mass>
<year>1969</year>
<geolocation>
<type>Point</type>
<coordinates>
<coordinate>-105.31667</coordinate>
<coordinate>26.96667</coordinate>
</coordinates>
</geolocation>
</meteor>
</meteors>
</data>
</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
| key | value |
|---|---|
| count | 1 |
| filteredOn | [name] |
| meteors | [{name:Allende,recclass:CV3,mass:2000000,year:1969,geolocation:{type:Point,coordinates:[-105.31667,26.96667]}}] |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
count | number | Total number of meteorites matching the search criteria | |
filteredOn | array | Array of field names used to filter the meteorite results | |
| [ ] Array items: | array[1] | Array of meteorite objects matching the search query | |
â”” name | string | - | |
â”” recclass | string | - | |
â”” mass | string | - | |
â”” year | string | - | |
â”” geolocation | object | - | |
â”” type | string | - | |
â”” coordinates | array | - |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Meteorite Landings through GraphQL to combine it with other API calls in a single request. Query only the meteorite landings data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
meteorites(
input: {
name: "Allende"
mass: 100
year: 1969
}
) {
count
filteredOn
meteors
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Meteorite Landings API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Meteorite Landings requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Meteorite Landings API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Meteorite Landings
Official Meteorite Landings packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Meteorite Landings works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Meteorite Landings?
How many credits does Meteorite Landings cost?
Each successful Meteorite Landings API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful meteorite landings lookups.
Can I use Meteorite Landings in production?
The free plan is for testing and development only. For production use of Meteorite Landings, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Meteorite Landings from a browser?
What happens if I exceed my Meteorite Landings credit limit?
When you reach your monthly credit limit, Meteorite Landings API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








