POST · VEDIC

Vimshottari Mahadasha

Endpoint POST https://starsapi.com/api/v3/vedic/dashas/vimshottari-mahadasha

Returns the 9 Mahadasha periods of the 120-year Vimshottari cycle, plus Moon nakshatra info, dasha balance at birth, and the currently running dasha at all 5 levels (MD → AD → PD → SD → Pran).

This is the starting point of the Vimshottari lazy-load chain. Sub-periods are fetched on demand via separate endpoints — keeping the initial payload under 3 KB.

Lazy-load chain
vimshottari-mahadashaantardashapratyantardashasookshmapran

Authentication

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

Request body

FieldTypeRequiredDescription
yearintegerYesBirth year, 4-digit.
monthintegerYesBirth month, 112.
dayintegerYesDay of month.
hourintegerYesHour, 24-hour format.
minuteintegerYesMinute.
secondintegerNoDefault 0.
latitudenumberYesDecimal degrees, −90…90.
longitudenumberYesDecimal degrees, −180…180.
timezonestringYesIANA timezone identifier.
ayanamsastringNoDefault lahiri. Full list →
node_typestringNomean (default) or true.
reference_datestringNoYYYY-MM-DD. Compute “current dasha” as of this date.

Ayanamsa & KP usage

Vimshottari periods are derived from the Moon’s nakshatra position, which shifts with the chosen ayanamsa. Lahiri and Krishnamurti (KP) differ by roughly 5–6 arc-minutes — enough to shift dasha start/end dates by several days, and at deeper levels (Sookshma/Pran) even change the running lord. KP practitioners should pass "ayanamsa": "krishnamurti" (alias kp); variants kp_new and kp_senthil are also supported. The ayanamsa actually used is echoed in the response meta for verification. Unknown ayanamsa names return an error rather than silently falling back to Lahiri.

Response shape

moon_nakshatra

FieldTypeDescription
namestringNakshatra name.
numberinteger1–27.
lordstringNakshatra lord (first Mahadasha planet).
degree_in_nakshatranumberMoon’s degree within the nakshatra (0–13.33).
percentage_traversednumberDetermines dasha balance.

current_dasha

Always returns all 5 levels regardless of this being an MD-only endpoint.

FieldTypeDescription
mahadashaobjectplanet, start_date, end_date, remaining.
antardashaobjectSame fields.
pratyantardashaobjectSame fields.
sookshma_dashaobjectSame fields (datetime format).
pran_dashaobjectSame fields (datetime format).
summarystringe.g. Ketu-Mercury-Sun-Mars-Saturn

mahadasha_table

9 Mahadasha entries covering the full 120-year cycle. No nested sub-periods.

FieldTypeDescription
planetstringDasha lord.
yearsintegerFull period duration in years.
start_datestringYYYY-MM-DD.
end_datestringYYYY-MM-DD.
is_balancebooleantrue for the first (balance) period.
is_currentbooleantrue for the currently active Mahadasha.

The 9 Dasha Lords

PlanetYears
Ketu7
Venus20
Sun6
Moon10
Mars7
Rahu18
Jupiter16
Saturn19
Mercury17

Total cycle: 120 years.

Next step: Antardasha

To see the 9 sub-periods within a Mahadasha, pass the planet value from the tapped row to the Antardasha endpoint.

Errors

HTTPCodeCause
400MISSING_FIELDRequired field absent.
400INVALID_DATEBad calendar date.
400INVALID_TIMEHour/minute/second out of range.
400INVALID_TIMEZONENon-IANA timezone.
400INVALID_COORDINATELat/lon out of range.
400INVALID_PARAMreference_date not YYYY-MM-DD.
405METHOD_NOT_ALLOWEDNon-POST request.
500COMPUTE_ERRORUnknown ayanamsa name.

See also