Docs/APIs/Planet Positions

Planet Positions

Get planet positions data

OperationalCredits 1 per callp50 285msAstrologyStar

Overview

Planet Positions works by analyzing the data provided and returning the position of planets in the solar system. It uses various sources to determine the position of planets in the solar system and returns the 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.

POSThttps://api.apiverve.com/v1/planetpositions
curl -X POST https://api.apiverve.com/v1/planetpositions \
  -H "x-api-key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "planet": "Moon",
  "date": "2025-04-15 10:37:00",
  "lat": 37.7749,
  "lon": -122.4194,
  "alt": 52
}'
const res = await fetch('https://api.apiverve.com/v1/planetpositions', {
  method: 'POST',
  headers: {
    'x-api-key': 'your_api_key_here',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "planet": "Moon",
  "date": "2025-04-15 10:37:00",
  "lat": 37.7749,
  "lon": -122.4194,
  "alt": 52
}),
});

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

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

res = requests.post(
    "https://api.apiverve.com/v1/planetpositions",
    headers={"x-api-key": "your_api_key_here"},
    json={
    "planet": "Moon",
    "date": "2025-04-15 10:37:00",
    "lat": 37.7749,
    "lon": -122.4194,
    "alt": 52
},
    timeout=15,
)
res.raise_for_status()

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

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

func main() {
	body := strings.NewReader(`{
  "planet": "Moon",
  "date": "2025-04-15 10:37:00",
  "lat": 37.7749,
  "lon": -122.4194,
  "alt": 52
}`)
	req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/planetpositions", body)
	req.Header.Set("Content-Type", "application/json")
	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 as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them.

ParameterTypeDescription
dateOptionalPremiumstringThe date to get planetary 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
latRequirednumberThe latitude of the observer
range -90–90
lonRequirednumberThe longitude of the observer
range -180–180
altOptionalnumberThe altitude of the observer in meters
range 0–∞
planetRequiredstringThe planet to get position data for
sunmoonmercuryvenusmarsjupitersaturnuranus+2

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": {
    "planet": "Moon",
    "isBelowHorizon": false,
    "date": "2025-04-15T10:37:00Z",
    "observer": {
      "latitude": 37.7749,
      "longitude": -122.4194
    },
    "rightAscension": {
      "hours": 15,
      "minutes": 13,
      "seconds": 11
    },
    "declination": {
      "degrees": -23,
      "minutes": 10,
      "seconds": 56
    },
    "distance": {
      "km": 402457.36,
      "lightTravelSeconds": 1.342,
      "astronomicalUnits": 0.003
    },
    "siderealTime": {
      "hours": 16,
      "minutes": 2,
      "seconds": 42
    },
    "hourAngle": {
      "hours": 0,
      "minutes": 49,
      "seconds": 31
    },
    "vectors": {
      "x": -0.0016452947779903913,
      "y": -0.0018463324771434563,
      "z": -0.0010590407236111441
    }
  }
}

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
planetstring"Moon"Name of the celestial body being observed
isBelowHorizonbooleanfalseWhether the planet is below horizon at observation location
datestring"2025-04-15T10:37:00Z"Observation date and time in ISO 8601 format
observerobject{...}
latitudenumber37.7749Observer latitude in decimal degrees
longitudenumber-122.4194Observer longitude in decimal degrees
rightAscensionPremiumobject{...}Right ascension coordinates of the planet
hoursPremiumnumber15Right ascension hours component (0-23)
minutesPremiumnumber13Right ascension minutes component (0-59)
secondsPremiumnumber11Right ascension seconds component (0-59)
declinationPremiumobject{...}Declination coordinates of the planet
degreesPremiumnumber-23Declination degrees component (-90 to 90)
minutesPremiumnumber10Declination minutes component (0-59)
secondsPremiumnumber56Declination seconds component (0-59)
distancePremiumobject{...}Distance to the planet in various units
kmPremiumnumber402457.36Distance to planet in kilometers
lightTravelSecondsPremiumnumber1.342Light travel time in seconds from planet
astronomicalUnitsPremiumnumber0.003Distance in astronomical units (AU)
siderealTimePremiumobject{...}Local sidereal time at observation
hoursPremiumnumber16Local sidereal time hours component (0-23)
minutesPremiumnumber2Local sidereal time minutes component (0-59)
secondsPremiumnumber42Local sidereal time seconds component (0-59)
hourAnglePremiumobject{...}Hour angle from the meridian
hoursPremiumnumber0Hour angle hours component from meridian
minutesPremiumnumber49Hour angle minutes component from meridian
secondsPremiumnumber31Hour angle seconds component from meridian
vectorsPremiumobject{...}Position vector components
xPremiumnumber-0.0016452947779903913X component of planet position vector
yPremiumnumber-0.0018463324771434563Y component of planet position vector
zPremiumnumber-0.0010590407236111441Z component of planet position vector

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.

Other ways to use Planet Positions

Set up Planet Positions 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.VerveKitReference →
Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheetsReference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContextReference →

More in Astrology:

Was this page helpful?