POST · VEDIC

Planets Advanced

Endpoint POST https://starsapi.com/api/v3/vedic/natal/planets-advanced

Returns all 9 Vedic grahas with the full baseline fields from /natal/planets plus deep analytical fields: KP sub-lords, functional nature (benefic/malefic/neutral for this specific ascendant), dignity booleans, Navamsa sign, vargottama status, and the complete 4-fold avastha system (Baladi, Deeptadi, Jagradi, Lajjitadi).

This is the most detailed planet endpoint — designed for professional astrologers, KP practitioners, and advanced interpretation engines. For baseline data only, use /natal/planets.

Authentication

Required. Three methods accepted:

MethodExample
Header (recommended)X-Api-Key: am_live_xxxxxxxxxxxx
BearerAuthorization: Bearer am_live_xxxxxxxxxxxx
Query?api_key=am_live_xxxxxxxxxxxx

See authentication for security considerations.

Request body

Identical to /natal/planets. All core fields are required.

FieldTypeRequiredDescription
yearintegerYesBirth year, 4-digit.
monthintegerYesBirth month, 112.
dayintegerYesDay of month.
hourintegerYesHour, 023.
minuteintegerYesMinute, 059.
secondintegerNoDefault 0.
latitudenumberYesSigned decimal degrees, −90…90.
longitudenumberYesSigned decimal degrees, −180…180.
timezonestringYesIANA timezone identifier.
namestringNoUse /vedic/birth-details to retrieve.
placestringNoUse /vedic/birth-details to retrieve.
ayanamsastringNoDefault lahiri. Full list →
node_typestringNomean (default) or true.

Response shape

All baseline fields from /natal/planets are included. The tables below document only the additional fields. The sample shows 2 representative planets — all 9 follow the same shape.

Ascendant — additional fields

FieldTypeDescription
sub_lordstringKP sub-lord of the ascendant degree.
sub_sub_lordstringKP sub-sub-lord.
functional_naturestringAlways Self for the ascendant.
functional_typestringAlways Ascendant.
functional_housesstringAlways 1st house.
navamsa_signstringNavamsa (D9) sign of the ascendant.
navamsa_sign_numintegerNavamsa sign number (1–12).
is_vargottamabooleantrue if Rashi and Navamsa sign are the same.

Planet — additional fields

FieldTypeDescription
KP
sub_lordstringKP sub-lord based on the planet’s longitude.
sub_sub_lordstringKP sub-sub-lord.
Functional nature (ascendant-specific)
functional_naturestringBenefic, Malefic, or Neutral for this ascendant.
functional_typestringReasoning (e.g. Trikona Lord, Dusthana Lord).
functional_housesstringWhich houses drive the classification (e.g. 2nd & 9th lord).
Dignity booleans
is_exaltedbooleanPlanet is in its sign of exaltation.
is_debilitatedbooleanPlanet is in its sign of debilitation.
is_own_signbooleanPlanet is in a sign it rules.
is_moolatrikonabooleanPlanet is in its moolatrikona range.
Divisional
navamsa_signstringNavamsa (D9) sign.
navamsa_sign_numintegerNavamsa sign number (1–12).
is_vargottamabooleantrue if Rashi sign equals Navamsa sign.
Avasthas (4-fold system)
avastha.balaobjectBaladi avastha: avastha (name), state (meaning), strength (0–100).
avastha.deeptadiobjectDeeptadi avastha: avastha, state (e.g. Exalted, Own Sign, Enemy Sign), effect.
avastha.jagradiobjectJagradi avastha: avastha (Jagrad/Swapna/Sushupt), state, strength.
avastha.lajjitadiobjectLajjitadi avastha: avastha, state, effect.

Use cases

  • KP analysis — use sub_lord and sub_sub_lord for Krishnamurti Paddhati predictions.
  • Yogakaraka detectionfunctional_nature + functional_houses identify yogakarakas and maraka lords programmatically.
  • Navamsa overlay — display Rashi and Navamsa sign side by side; flag vargottama planets.
  • Avastha-based predictions — the 4-fold avastha system gives a multi-dimensional strength profile for each planet.
  • Professional reports — all the data a Jyotish practitioner needs in a single call.

Errors

HTTPCodeCause
400MISSING_FIELDA required birth field is absent.
400INVALID_DATEInvalid calendar date.
400INVALID_TIMEHour/minute/second out of range.
400INVALID_TIMEZONENumeric or non-IANA timezone.
400INVALID_COORDINATElatitude / longitude out of range.
401AUTH_MISSING_KEYNo API key in request.
401AUTH_INVALID_KEYKey format invalid or not found.
401AUTH_REVOKED_KEYKey has been revoked.
403AUTH_ORIGIN_DENIEDRequest from non-whitelisted origin.
405METHOD_NOT_ALLOWEDNon-POST request.
429RATE_LIMIT_EXCEEDEDPlan quota exceeded.
500CALCULATION_ERROREphemeris calculation failed.

Error response format

{
  "success": false,
  "error": {
    "code": "INVALID_TIMEZONE",
    "message": "Unrecognised timezone: 'Asia/Calcutta_'. Use a valid IANA identifier such as 'Asia/Kolkata'."
  }
}

See also