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
Method
Example
Header (recommended)
X-Api-Key: am_live_xxxxxxxxxxxx
Bearer
Authorization: Bearer am_live_xxxxxxxxxxxx
Query
?api_key=am_live_xxxxxxxxxxxx
Request body
Field
Type
Required
Description
year
integer
Yes
Birth year, 1800–2400.
month
integer
Yes
Birth month, 1–12.
day
integer
Yes
Day of month.
hour
integer
Yes
Hour, 0–23.
minute
integer
Yes
Minute, 0–59.
second
integer
No
Default 0.
latitude
number
Yes
Decimal degrees.
longitude
number
Yes
Decimal degrees.
timezone
string
Yes
IANA timezone identifier.
ayanamsa
string
No
Default lahiri.
node_type
string
No
mean (default) or true.
language
string
No
Default 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:
Field
Type
Description
title
string
e.g. "Sun in Taurus".
planet
string
Planet name.
sign
string
Sidereal sign name.
sign_lord
string
Lord of the sign.
nakshatra
string
Nakshatra name.
nakshatra_pada
integer
Pada 1–4.
is_retro
boolean
Retrograde status.
degree
number
Degree within sign.
text
string
Detailed interpretation paragraph.
keywords
array
5 keyword strings.
Errors
HTTP
Code
Cause
400
MISSING_FIELD
Required field absent.
400
INVALID_DATE
Year out of range or bad calendar date.
400
INVALID_TIMEZONE
Non-IANA timezone.
400
INVALID_COORDINATE
Latitude or longitude out of range.
400
INVALID_PARAM
Bad node_type, ayanamsa, or language.
405
METHOD_NOT_ALLOWED
Non-POST request.
500
COMPUTE_ERROR
Chart 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.