Moon Position API
Overview
To use Moon Position, 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/moonpositionExample
How to call the Moon Position API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/moonposition?lat=37.7749&lon=-122.4194&date=01-16-2026&time=14%3A30" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/moonposition?lat=37.7749&lon=-122.4194&date=01-16-2026&time=14%3A30', {
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/moonposition?lat=37.7749&lon=-122.4194&date=01-16-2026&time=14%3A30', 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/moonposition?lat=37.7749&lon=-122.4194&date=01-16-2026&time=14%3A30", 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": {
"date": "01-22-2026",
"time": "14:30",
"coordinates": {
"latitude": 37.7749,
"longitude": -122.4194
},
"moon": {
"altitude": -0.407908976399288,
"azimuth": 1.4720499058762104,
"distance": 404332.6834067969
}
}
}Authentication
The Moon Position 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 Moon Position API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Moon Position API:
Get Moon Position Data
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
lat | number | required | The latitude of the location Range: -90 - 90 | - | |
lon | number | required | The longitude of the location Range: -180 - 180 | - | |
datePremium | string | optional | The date to get the moon position data for (MM-dd-yyyy) Format: date (e.g., 01-16-2026) | - | |
time | string | optional | The time of day for the calculation (HH:mm format, 24-hour). Defaults to 00:00 if not provided Format: time (e.g., 14:30) | - |
Response
The Moon Position 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>
<date>01-22-2026</date>
<time>14:30</time>
<coordinates>
<latitude>37.7749</latitude>
<longitude>-122.4194</longitude>
</coordinates>
<moon>
<altitude>-0.407908976399288</altitude>
<azimuth>1.4720499058762104</azimuth>
<distance>404332.6834067969</distance>
</moon>
</data>
</response>
status: ok
error: null
data:
date: 01-22-2026
time: '14:30'
coordinates:
latitude: 37.7749
longitude: -122.4194
moon:
altitude: -0.407908976399288
azimuth: 1.4720499058762104
distance: 404332.6834067969
| key | value |
|---|---|
| date | 01-22-2026 |
| time | 14:30 |
| coordinates | {latitude:37.7749,longitude:-122.4194} |
| moon | {altitude:-0.407908976399288,azimuth:1.4720499058762104,distance:404332.6834067969} |
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 |
|---|---|---|---|
date | string | The date for which moon position was calculated | |
time | string | The time of observation in HH:MM format | |
coordinates | object | - | |
â”” latitude | number | The latitude coordinate of the observation location | |
â”” longitude | number | The longitude coordinate of the observation location | |
moon | object | - | |
â”” altitude | number | Moon altitude in degrees, calculated from observation location | |
â”” azimuthPremium | number | Moon azimuth in radians, derived astronomical calculation | |
â”” distancePremium | number | Distance from observer to moon in kilometers |
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 Moon Position through GraphQL to combine it with other API calls in a single request. Query only the moon position 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 {
moonposition(
input: {
lat: 37.7749
lon: -122.4194
date: "01-16-2026"
time: "14:30"
}
) {
date
time
coordinates {
latitude
longitude
}
moon {
altitude
azimuth
distance
}
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Moon Position 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
Moon Position 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 Moon Position 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 Moon Position
Official Moon Position packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Moon Position 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 Moon Position?
How many credits does Moon Position cost?
Each successful Moon Position 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 moon position lookups.
Can I use Moon Position in production?
The free plan is for testing and development only. For production use of Moon Position, 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 Moon Position from a browser?
What happens if I exceed my Moon Position credit limit?
When you reach your monthly credit limit, Moon Position 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.








