Planet Positions API POST

Planet Positions is a simple tool for getting the position of planets in the solar system. It returns the position of planets in the solar system.

Try it — live request, no key required

Request

POSTapi.apiverve.com/v1/planetpositions

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Planet Positions response payload
  }
}

About the Planet Positions API

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.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use Planet Positions

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the Planet Positions API.

Read the docs →

What does the Planet Positions API do?

Planet Positions is a simple tool for getting the position of planets in the solar system. It returns the position of planets in the solar system.

How do I authenticate Planet Positions API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Planet Positions API cost?

Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Planet Positions API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Planet Positions API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Planet Positions API use?

POST over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — POST /v1/planetpositions

Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`lat`Required	number	`37.7749`	The latitude of the observer range -90-90
`lon`Required	number	`-122.4194`	The longitude of the observer range -180-180
`planet`Required	string	`mars`	The planet to get position data for `sunmoonmercuryvenusmarsjupitersaturnuranus`+2

Optional

Parameter	Type	Example	Description
`date`OptionalPremium	string	`01-16-2026`	The date to get planetary position data for (MM-DD-YYYY) date
`time`Optional	string	`21:00`	The time of day for the calculation (HH:mm format, 24-hour). Defaults to 00:00 if not provided time
`alt`Optional	number	`0`	The altitude of the observer in meters default 0 · range 0-inf

Example request

curl -X POST "https://api.apiverve.com/v1/planetpositions" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"lat":37.7749,"lon":-122.4194,"planet":"Moon","date":"2025-04-15 10:37:00","time":"value","alt":52}'

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.
`content-type`Required	POST body	`application/json`

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.

Response — POST /v1/planetpositions

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

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.

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
`rightAscension`Premium	object	`{...}`	Right ascension coordinates of the planet
`hours`Premium	number	`15`	Right ascension hours component (0-23)
`minutes`Premium	number	`13`	Right ascension minutes component (0-59)
`seconds`Premium	number	`11`	Right ascension seconds component (0-59)
`declination`Premium	object	`{...}`	Declination coordinates of the planet
`degrees`Premium	number	`-23`	Declination degrees component (-90 to 90)
`minutes`Premium	number	`10`	Declination minutes component (0-59)
`seconds`Premium	number	`56`	Declination seconds component (0-59)
`distance`Premium	object	`{...}`	Distance to the planet in various units
`km`Premium	number	`402457.36`	Distance to planet in kilometers
`lightTravelSeconds`Premium	number	`1.342`	Light travel time in seconds from planet
`astronomicalUnits`Premium	number	`0.003`	Distance in astronomical units (AU)
`siderealTime`Premium	object	`{...}`	Local sidereal time at observation
`hours`Premium	number	`16`	Local sidereal time hours component (0-23)
`minutes`Premium	number	`2`	Local sidereal time minutes component (0-59)
`seconds`Premium	number	`42`	Local sidereal time seconds component (0-59)
`hourAngle`Premium	object	`{...}`	Hour angle from the meridian
`hours`Premium	number	`0`	Hour angle hours component from meridian
`minutes`Premium	number	`49`	Hour angle minutes component from meridian
`seconds`Premium	number	`31`	Hour angle seconds component from meridian
`vectors`Premium	object	`{...}`	Position vector components
`x`Premium	number	`-0.0016452947779903913`	X component of planet position vector
`y`Premium	number	`-0.0018463324771434563`	Y component of planet position vector
`z`Premium	number	`-0.0010590407236111441`	Z component of planet position vector

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	Planet Positions calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — POST /v1/planetpositions

No SDK to install — this is a plain HTTPS call to /v1/planetpositions with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/planetpositions" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/planetpositions-apiSource, issues and the examples this page is built from.ReferencePlanet Positions API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/planetpositionsnpm APIVerve.API.PlanetPositionsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — POST /v1/planetpositions

Install the Node.js SDK, then call the Planet Positions API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/planetpositions

Node.js

const res = await fetch("https://api.apiverve.com/v1/planetpositions", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/planetpositionsThe published Node.js client, versioned and signed.GitHubapiverve/planetpositions-apiSource, issues and the examples this page is built from.ReferencePlanet Positions API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.PlanetPositionsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — POST /v1/planetpositions

No SDK to install — this is a plain HTTPS call to /v1/planetpositions with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/planetpositions",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/planetpositionsnpm APIVerve.API.PlanetPositionsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — POST /v1/planetpositions

Install the C# / .NET SDK, then call the Planet Positions API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.PlanetPositions

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/planetpositions");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.PlanetPositionsThe published C# / .NET client, versioned and signed.GitHubapiverve/planetpositions-apiSource, issues and the examples this page is built from.ReferencePlanet Positions API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/planetpositionsnpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — POST /v1/planetpositions

No SDK to install — this is a plain HTTPS call to /v1/planetpositions with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/planetpositions", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/planetpositionsnpm APIVerve.API.PlanetPositionsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — POST /v1/planetpositions

No SDK to install — this is a plain HTTPS call to /v1/planetpositions with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/planetpositions");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/planetpositionsnpm APIVerve.API.PlanetPositionsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — POST /v1/planetpositions

No SDK to install — this is a plain HTTPS call to /v1/planetpositions with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/planetpositions")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/planetpositionsnpm APIVerve.API.PlanetPositionsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

Add Daily Horoscopes to Your App in 5 MinutesBuild a horoscope feature your users will actually check daily. Working code included.Read

Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read

Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read

Planet Positions API POST

Try it — live request, no key required

About the Planet Positions API

Ways to call it

Other ways to use Planet Positions

Questions.

Request parameters — POST /v1/planetpositions

Required

Optional

Authentication

Response — POST /v1/planetpositions

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — POST /v1/planetpositions

Resources

Also published for

Call it from Node.js — POST /v1/planetpositions

Resources

Also published for

Call it from Python — POST /v1/planetpositions

Resources

Also published for

Call it from C# / .NET — POST /v1/planetpositions

Resources

Also published for

Call it from Go — POST /v1/planetpositions

Resources

Also published for

Call it from PHP — POST /v1/planetpositions

Resources

Also published for

Call it from Ruby — POST /v1/planetpositions

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Planet Positions API

Astrology

Related articles

Ready to build with Planet Positions? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog