Moon Position API Reference

Overview

Moon Position works by analyzing the location provided and calculating moon position data. It uses advanced algorithms to calculate data such as altitude, azimuth, and distance of the moon from the location and returns the moon position data.

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

curl "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 res = await fetch('https://api.apiverve.com/v1/moonposition?lat=37.7749&lon=-122.4194&date=01-16-2026&time=14%3A30', {
  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/moonposition?lat=37.7749&lon=-122.4194&date=01-16-2026&time=14%3A30",
    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/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")

	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
`lat`Required	number	The latitude of the location range -90–90
`lon`Required	number	The longitude of the location range -180–180
`date`OptionalPremium	string	The date to get the moon position data for (MM-dd-yyyy) date
`time`Optional	string	The time of day for the calculation (HH:mm format, 24-hour). Defaults to 00:00 if not provided time

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": {
    "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 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
`date`	string	`"01-22-2026"`	The date for which moon position was calculated
`time`	string	`"14:30"`	The time of observation in HH:MM format
`coordinates`	object	`{...}`
`latitude`	number	`37.7749`	The latitude coordinate of the observation location
`longitude`	number	`-122.4194`	The longitude coordinate of the observation location
`moon`	object	`{...}`
`altitude`	number	`-0.407908976399288`	Moon altitude in degrees, calculated from observation location
`azimuth`Premium	number	`1.4720499058762104`	Moon azimuth in radians, derived astronomical calculation
`distance`Premium	number	`404332.6834067969`	Distance from observer to moon in kilometers

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: Use the Moon Position API to get moon position data for astronomy. Use the data to track lunar events, observe celestial phenomena, and enhance stargazing
Photography: Get moon position data by using the Moon Position API for photography. Use the data to plan photo shoots, optimize lighting conditions, and capture stunning images
Outdoor Activities: Use the Moon Position API to get moon position data for outdoor activities. Use the data to plan outdoor events, schedule activities, and enhance experiences
Lunar Calendar: Get moon position data by using the Moon Position API for lunar calendar. Use the data to track lunar phases, plan events, and follow lunar cycles

Other ways to use Moon Position

Set up Moon Position 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 →

Moon Position