Planet PositionsPlanet Positions API

OnlineCredit Usage:1 per callRefreshed 1 month ago
avg: 301ms|p50: 285ms|p75: 312ms|p90: 344ms|p99: 409ms

Overview

To use Planet Positions, you need an API key. You can get one by creating a free account and visiting your dashboard.

POST Endpoint

URL
https://api.apiverve.com/v1/planetpositions

Example

How to call the Planet Positions API in different programming languages.

cURL Request
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
}'
JavaScript (Fetch API)
const response = 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
})
});

const data = await response.json();
console.log(data);
Python (Requests)
import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

payload = {
    "planet": "Moon",
    "date": "2025-04-15 10:37:00",
    "lat": 37.7749,
    "lon": -122.4194,
    "alt": 52
}

response = requests.post('https://api.apiverve.com/v1/planetpositions', headers=headers, json=payload)

data = response.json()
print(data)
Go (net/http)
package main

import (
    "fmt"
    "io"
    "net/http"
    "bytes"
    "encoding/json"
)

func main() {
    payload := map[string]interface{}{
        "planet": "Moon",
        "date": "2025-04-15 10:37:00",
        "lat": "37.7749",
        "lon": "-122.4194",
        "alt": "52"
    }

    jsonPayload, _ := json.Marshal(payload)
    req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/planetpositions", bytes.NewBuffer(jsonPayload))

    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))
}
Example 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
    }
  }
}

Authentication

The Planet Positions API requires authentication via API key. Include your API key in the request header:

Required Header
X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the Planet Positions API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the Planet Positions API:

Some Planet Positions parameters marked with Premium are available exclusively on paid plans.View pricing

Get Planet Position Data

ParameterTypeRequiredDescriptionDefaultExample
datePremiumstringoptional
The date to get planetary position data for (MM-DD-YYYY)
Format: date (e.g., 01-16-2026)
-01-16-2026
timestringoptional
The time of day for the calculation (HH:mm format, 24-hour). Defaults to 00:00 if not provided
Format: time (e.g., 21:00)
-21:00
latnumberrequired
The latitude of the observer
Range: -90 - 90
-37.7749
lonnumberrequired
The longitude of the observer
Range: -180 - 180
--122.4194
altnumberoptional
The altitude of the observer in meters
Range: min: 0
-52
planetstringrequired
The planet to get position data for
Supported values: sunmoonmercuryvenusmars
-mars

Response

The Planet Positions 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 Response
200 OK
<?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>
    <planet>Moon</planet>
    <isBelowHorizon>false</isBelowHorizon>
    <date>2025-04-15T10:37:00Z</date>
    <observer>
      <latitude>37.7749</latitude>
      <longitude>-122.4194</longitude>
    </observer>
    <rightAscension>
      <hours>15</hours>
      <minutes>13</minutes>
      <seconds>11</seconds>
    </rightAscension>
    <declination>
      <degrees>-23</degrees>
      <minutes>10</minutes>
      <seconds>56</seconds>
    </declination>
    <distance>
      <km>402457.36</km>
      <lightTravelSeconds>1.342</lightTravelSeconds>
      <astronomicalUnits>0.003</astronomicalUnits>
    </distance>
    <siderealTime>
      <hours>16</hours>
      <minutes>2</minutes>
      <seconds>42</seconds>
    </siderealTime>
    <hourAngle>
      <hours>0</hours>
      <minutes>49</minutes>
      <seconds>31</seconds>
    </hourAngle>
    <vectors>
      <x>-0.0016452947779903913</x>
      <y>-0.0018463324771434563</y>
      <z>-0.0010590407236111441</z>
    </vectors>
  </data>
</response>
YAML Response
200 OK
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
CSV Response
200 OK
keyvalue
planetMoon
isBelowHorizonfalse
date2025-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 Structure

All API responses follow a consistent structure with the following fields:

FieldTypeDescriptionExample
statusstringIndicates whether the request was successful ("ok") or failed ("error")ok
errorstring | nullContains error message if status is "error", otherwise nullnull
dataobject | nullContains 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:

Response fields marked with Premium are available exclusively on paid plans.View pricing
FieldTypeSample ValueDescription
planetstring"Moon"
Name of the celestial body being observed
isBelowHorizonbooleanfalse
Whether the planet is below horizon at observation location
datestring"2025-04-15T10:37:00Z"
Observation date and time in ISO 8601 format
observerobject{...}
-
â”” latitudenumber37.7749
Observer latitude in decimal degrees
â”” longitudenumber-122.4194
Observer longitude in decimal degrees
rightAscensionPremiumobject{...}
Right ascension coordinates of the planet
â”” hoursnumber15
Right ascension hours component (0-23)
â”” minutesnumber13
Right ascension minutes component (0-59)
â”” secondsnumber11
Right ascension seconds component (0-59)
declinationPremiumobject{...}
Declination coordinates of the planet
â”” degreesnumber-23
Declination degrees component (-90 to 90)
â”” minutesnumber10
Declination minutes component (0-59)
â”” secondsnumber56
Declination seconds component (0-59)
distancePremiumobject{...}
Distance to the planet in various units
â”” kmnumber402457.36
Distance to planet in kilometers
â”” lightTravelSecondsnumber1.342
Light travel time in seconds from planet
â”” astronomicalUnitsnumber0.003
Distance in astronomical units (AU)
siderealTimePremiumobject{...}
Local sidereal time at observation
â”” hoursnumber16
Local sidereal time hours component (0-23)

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 Planet Positions through GraphQL to combine it with other API calls in a single request. Query only the planet positions data you need with precise field selection, and orchestrate complex data fetching workflows.

Test Planet Positions in the GraphQL Explorer to confirm availability and experiment with queries.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

GraphQL Endpoint
POST https://api.apiverve.com/v1/graphql
GraphQL Query Example
query {
  planetpositions(
    input: {
      planet: "Moon"
      date: "2025-04-15 10:37:00"
      lat: 37.7749
      lon: -122.4194
      alt: 52
    }
  ) {
    planet
    isBelowHorizon
    date
    observer {
      latitude
      longitude
    }
    rightAscension {
      hours
      minutes
      seconds
    }
    declination {
      degrees
      minutes
      seconds
    }
    distance {
      km
      lightTravelSeconds
      astronomicalUnits
    }
    siderealTime {
      hours
      minutes
      seconds
    }
    hourAngle {
      hours
      minutes
      seconds
    }
    vectors {
      x
      y
      z
    }
  }
}

Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.

CORS Support

The Planet Positions 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

Planet Positions 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 Planet Positions 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 Planet Positions

Official Planet Positions packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →

No-Code Integrations

Planet Positions 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 Planet Positions?
Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for Planet Positions and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
How many credits does Planet Positions cost?

Each successful Planet Positions 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 planet positions lookups.

Can I use Planet Positions in production?

The free plan is for testing and development only. For production use of Planet Positions, 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 Planet Positions from a browser?
Yes! The Planet Positions API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.
What happens if I exceed my Planet Positions credit limit?

When you reach your monthly credit limit, Planet Positions 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.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?