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.
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.
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.
| Parameter | Type | Description |
|---|---|---|
dateOptionalPremium | string | The date to get planetary position data for (MM-DD-YYYY) date |
timeOptional | string | The time of day for the calculation (HH:mm format, 24-hour). Defaults to 00:00 if not provided time |
latRequired | number | The latitude of the observer range -90–90 |
lonRequired | number | The longitude of the observer range -180–180 |
altOptional | number | The altitude of the observer in meters range 0–∞ |
planetRequired | string | The planet to get position data forsunmoonmercuryvenusmarsjupitersaturnuranus+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.
{
"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.
| Field | Type | Example | Description |
|---|---|---|---|
planet | string | "Moon" | Name of the celestial body being observed |
isBelowHorizon | boolean | false | Whether the planet is below horizon at observation location |
date | string | "2025-04-15T10:37:00Z" | Observation date and time in ISO 8601 format |
observer | object | {...} | |
latitude | number | 37.7749 | Observer latitude in decimal degrees |
longitude | number | -122.4194 | Observer longitude in decimal degrees |
rightAscensionPremium | object | {...} | Right ascension coordinates of the planet |
hoursPremium | number | 15 | Right ascension hours component (0-23) |
minutesPremium | number | 13 | Right ascension minutes component (0-59) |
secondsPremium | number | 11 | Right ascension seconds component (0-59) |
declinationPremium | object | {...} | Declination coordinates of the planet |
degreesPremium | number | -23 | Declination degrees component (-90 to 90) |
minutesPremium | number | 10 | Declination minutes component (0-59) |
secondsPremium | number | 56 | Declination seconds component (0-59) |
distancePremium | object | {...} | Distance to the planet in various units |
kmPremium | number | 402457.36 | Distance to planet in kilometers |
lightTravelSecondsPremium | number | 1.342 | Light travel time in seconds from planet |
astronomicalUnitsPremium | number | 0.003 | Distance in astronomical units (AU) |
siderealTimePremium | object | {...} | Local sidereal time at observation |
hoursPremium | number | 16 | Local sidereal time hours component (0-23) |
minutesPremium | number | 2 | Local sidereal time minutes component (0-59) |
secondsPremium | number | 42 | Local sidereal time seconds component (0-59) |
hourAnglePremium | object | {...} | Hour angle from the meridian |
hoursPremium | number | 0 | Hour angle hours component from meridian |
minutesPremium | number | 49 | Hour angle minutes component from meridian |
secondsPremium | number | 31 | Hour angle seconds component from meridian |
vectorsPremium | object | {...} | Position vector components |
xPremium | number | -0.0016452947779903913 | X component of planet position vector |
yPremium | number | -0.0018463324771434563 | Y component of planet position vector |
zPremium | number | -0.0010590407236111441 | Z 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.
| 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. |
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.
Related
More in Astrology: