POST · VEDIC

Planet in Sign

Endpoint POST https://starsapi.com/api/v3/vedic/predictions/planet-in-sign

Returns Vedic sign-placement interpretations for all 9 planets based on their sidereal sign. Each entry includes sign, sign lord, nakshatra, and a detailed text interpretation with keywords. Coverage: 9 planets × 12 signs = 108 unique entries.

Authentication

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

Request body

FieldTypeRequiredDescription
yearintegerYesBirth year, 1800–2400.
monthintegerYesBirth month, 1–12.
dayintegerYesDay of month.
hourintegerYesHour, 0–23.
minuteintegerYesMinute, 0–59.
secondintegerNoDefault 0.
latitudenumberYesDecimal degrees.
longitudenumberYesDecimal degrees.
timezonestringYesIANA timezone identifier.
ayanamsastringNoDefault lahiri.
node_typestringNomean (default) or true.
languagestringNoDefault en. Supported: en, es, fr, pt, it, de, ru, hi, ta, te, kn, ml, bn.

Response shape

data.planets is an array of 9 objects (Sun through Ketu), each with:

FieldTypeDescription
titlestringe.g. "Sun in Taurus".
planetstringPlanet name.
signstringSidereal sign name.
sign_lordstringLord of the sign.
nakshatrastringNakshatra name.
nakshatra_padaintegerPada 1–4.
is_retrobooleanRetrograde status.
degreenumberDegree within sign.
textstringDetailed interpretation paragraph.
keywordsarray5 keyword strings.

Errors

HTTPCodeCause
400MISSING_FIELDRequired field absent.
400INVALID_DATEYear out of range or bad calendar date.
400INVALID_TIMEZONENon-IANA timezone.
400INVALID_COORDINATELatitude or longitude out of range.
400INVALID_PARAMBad node_type, ayanamsa, or language.
405METHOD_NOT_ALLOWEDNon-POST request.
500COMPUTE_ERRORChart computation failed.

Notes

  • Unlike Planet in House, this endpoint interprets by sign only — no house context. Use both together for a complete picture.
  • No ascendant object is returned since sign interpretations are lagna-independent.

See also