Docs/APIs/Moon Position

Moon Position

Get moon position data

OperationalCredits 2 per callp50 356msAstrologyStar

Overview

A moon and lunar position API. 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.

Live Test Moon Position API →

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&timezone=America%2FLos_Angeles" \
  -H "x-api-key: your_api_key_here"

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.

ParameterTypeDescription
latRequirednumberThe latitude of the location
range -90–90
lonRequirednumberThe longitude of the location
range -180–180
dateOptionalPremiumstringThe date to get the moon position data for (MM-dd-yyyy)
date
timeOptionalstringThe time of day for the calculation (HH:mm format, 24-hour). Defaults to 00:00 if not provided
time
timezoneOptionalstringIANA timezone name the date and time are given in. Defaults to the timezone of the supplied coordinates
timezone

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.

FieldTypeExampleDescription
datestring"01-22-2026"The date for which moon position was calculated
timestring"14:30"The time of observation in HH:MM format
coordinatesobject{...}The observation location the position was calculated for
latitudenumber37.7749The latitude coordinate of the observation location
longitudenumber-122.4194The longitude coordinate of the observation location
moonobject{...}The moon's position as seen from the observation location
altitudenumber-0.407908976399288Moon altitude above the horizon in radians, calculated from observation location. Negative values mean the moon is below the horizon
azimuthPremiumnumber1.4720499058762104Moon azimuth in radians, derived astronomical calculation
distancePremiumnumber404332.6834067969Distance 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.

StatusMeaningWhat to do
400Input was rejectedRead error; it names the parameter.
401Key missing or invalidCheck the header name and the key value.
403Key valid, but not permittedA key restriction or IP allow-list; see key scoping.
429Rate limited, or out of creditsRead error to tell them apart; see rate limits.

Start from a template

A working app built on this API, ready to deploy with your own key. Vercel asks for the key when you deploy; the code is on GitHub to change first.

Use cases

Night Photography Planning
Landscape photographers check moon altitude across evening hours to time foreground illumination and align night-sky shots.
Telescope Pointing Assistants
Amateur astronomy software plots lunar elevation by observer coordinates to guide telescope targeting during backyard stargazing sessions.
Coastal Night Navigation
When planning coastal night voyages, marine navigation tools track lunar altitude to anticipate natural visibility over open water.
Nocturnal Wildlife Research
Field biology platforms log lunar elevation against animal GPS tracks to correlate predator hunting patterns with ambient moonlight.

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 →
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 →

More in Astrology:

Was this page helpful?