POST/api/astro/planet_transit_natal_planets/1 credit

Transit over natal planet

Prewritten readings for one planet passing over another planet's birth position — transiting Saturn over the natal Moon, transiting Jupiter over the natal Sun, and so on. This is the pairwise transit table most transit reports are built from. It is a pure lookup with no chart calculation behind it: supply the transiting planet as `planet` and the birth-chart planet as `natal_planet` and you get the text back. Work out which contacts are actually live from a transit calculation such as `/api/astro/transit/` first, then call this for the wording. Both arguments accept the nine bodies, although the transiting side omits Venus. Order matters: Saturn over the natal Sun is a different entry from the Sun over natal Saturn.

https://yogataraapi.prahlad.app/api/astro/planet_transit_natal_planets/

Test Request

Authentication

Send your key in the X-API-Key header. Keys are server-side credentials — never put one in browser JavaScript or a mobile app.

X-API-Key: yt_live_a1b2c3d4_…
Content-Type: application/json

Request fields

Field	Type	Required	Notes
keys	array	required	Which calculations to return, as a list of names. See the key table for this endpoint; an unrecognised name rejects the whole request. One call costs one credit however many keys you ask for, so request everything you need at once rather than making several calls.
natal_planet	string	required	`sunmoonmarsmercuryjupitervenussaturnrahuketu` Exact lower-case match. All 9 are present under every transiting planet (verified by AST-parsing the mapping). An unknown value returns "Invalid key: <x>" with HTTP 200.
planet	string	required	`sunmoonmarsmercuryjupitersaturnrahuketu` NOTE: 'venus' is MISSING as a transiting planet - the mapping has only these 8 top-level keys. An unknown value returns "Invalid key: <x>" with HTTP 200.

Available keys (1)

Ask for exactly the calculations you want by listing them in keys. An unknown key rejects the whole request, and you are charged 1 credit however many you ask for — so batch them.

Key	Extra fields needed	Description
get_planet_transit_natal_planets	planet, natal_planet	The reading for `planet` transiting over the birth position of `natal_planet`. Returns a list of short phrases, usually two to four, each a separate statement about the contact. The pair is directional, so the transiting planet and the natal planet are not interchangeable.

Example request

curl -X POST https://yogataraapi.prahlad.app/api/astro/planet_transit_natal_planets/ \
  -H "X-API-Key: $OCCULT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"keys":["get_planet_transit_natal_planets"],"planet":"Sun","natal_planet":"sun"}'

Response

{
  "data": {
    "get_planet_transit_natal_planets": [
      "Start of a new solar cycle",
      "Brings new energy, optimism, and enthusiasm"
    ]
  },
  "status": 200,
  "is_error": false,
  "message": "successful"
}

Captured from a real call using the exact request above. Results sit under data, keyed by what you requested.

Errors

Metering errors return { "error": "…", "message": "<code>", "is_error": true }. Show error to people and branch on message. See the error reference.