POST · VEDIC

Dasha Sandhi

Endpoint POST https://starsapi.com/api/v3/vedic/matchmaking/dasha-sandhi

Returns dasha transition (sandhi) analysis for both persons — identifies upcoming Mahadasha changes and evaluates whether the transition periods overlap or create instability.

Works with both Ashtakoot and Porutham systems. All matchmaking endpoints use the same person1 / person2 request format.

Authentication

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

Request body

FieldTypeRequiredDescription
person1objectYesFirst person’s birth data (see fields below).
person2objectYesSecond person’s birth data (same fields).
Each person object:
yearintegerYesBirth year.
monthintegerYesBirth month, 1–12.
dayintegerYesDay of month.
hourintegerYesHour, 24-hour.
minuteintegerYesMinute.
secondintegerNoDefault 0.
latitudenumberYesDecimal degrees.
longitudenumberYesDecimal degrees.
timezonestringYesIANA timezone.
Optional (top-level):
ayanamsastringNoDefault lahiri.
node_typestringNomean (default) or true.

Response shape

person1 / person2

Upcoming Mahadasha transitions with dates and planets involved.

paired

Analysis of whether transitions overlap, creating a period of mutual instability.

Errors

HTTPCodeCause
400MISSING_FIELDRequired field absent.
400INVALID_DATEBad calendar date.
400INVALID_TIMEZONENon-IANA timezone.
400INVALID_COORDINATELat/lon out of range.
405METHOD_NOT_ALLOWEDNon-POST request.

See also