curl -X POST https://yogataraapi.prahlad.app/api/astro/planet_insights/ \
-H "X-API-Key: $OCCULT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"keys":["get_planet_sign_insight"],"planet":"Jupiter","sign":"aries","house":0,"nakshatra":"rohini"}'Prewritten interpretations for a single planet in a single position. Give it a planet and where that planet sits — a zodiac sign, a house, or a nakshatra — and it returns the classical reading for that combination. It is a lookup into a text corpus, not a calculation: no date, time or place is involved, and the same request always returns the same text. Use it to caption a chart you have already computed. Take Jupiter's sign, house and nakshatra from `/api/astro/chart/`, then call this endpoint for the wording. All three keys can be requested in one call, but each has its own extra parameter, so `planet`, `sign`, `house` and `nakshatra` must all be present in the body when you ask for all three. Coverage is nine planets (the seven plus Rahu and Ketu) across twelve signs and twelve houses. Nakshatra readings exist for the seven classical planets only — Rahu and Ketu have none. An unrecognised planet, sign, house or nakshatra comes back as an explanatory string with HTTP 200 rather than an error, so check what type you were given before rendering it.
| Field | Type | Required | Notes |
|---|---|---|---|
| house | integer | required | |
| 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. |
| nakshatra | string | required | ashwinibharanikrittikarohinimrigasiraaardrapunarvasupushyamiaasreshamakhapoorva phalguniuttara phalguniThe list above is the one used by jupiter, mercury, venus and saturn. 'rahu' and 'ketu' have no nakshatra data at all. Unmatched values return "Invalid nakshatra: <x> for planet <p>" with HTTP 200. |
| planet | string | required | sunmoonmarsmercuryjupitervenussaturnrahuketuAn unknown planet returns the string "Invalid planet: <x>" with HTTP 200, not an error status. Note rahu and ketu have NO nakshatra data (insights['rahu']['nakshatras'] is None), so get_planet_nakshatra_insight returns "No nakshatra data available for rahu". |
| sign | string | required | ariestaurusgeminicancerleovirgolibrascorpiosagittariuscapricornaquariuspiscesDATA BUG worth documenting: for planet='sun' the key is misspelled 'vigro' instead of 'virgo', so sun+virgo returns "Invalid sign: virgo for planet sun" while sun+vigro works. All eight other planets use 'virgo'. |
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_house_insight | planet, house | The reading for `planet` placed in a house, `house` being 1 to 12. Returns an object with the house label, a summary and trait lists, plus `classicalTexts` — a list of `{heading, text}` quoting Parashara, Brihat Jataka, Saravali and Phaladipika on that placement — and `houseLordVariations`, a list of `{ascendent, aspect, result}` giving how the reading changes for each of the twelve ascendants. Some of the summary and trait fields are null where only the classical quotations exist. | |
| get_planet_nakshatra_insight | planet, nakshatra | The reading for `planet` placed in `nakshatra`, returned as a single sentence or two of plain text rather than a structured object. Available for the seven classical planets across all 27 nakshatras; Rahu and Ketu have no nakshatra readings and return an explanatory string instead. | |
| get_planet_sign_insight | planet, sign | The reading for `planet` placed in `sign`. Returns an object with `sign` (the Sanskrit label for the combination, such as "Mesa Brhaspati"), a `summary` paragraph, and the lists `core traits`, `psychologicalPhysicalTraits`, `astrologicalReasoning` and `drstiphala`, the last covering the effects of that planet's aspects from there. Note the space in the `core traits` field name. |