POST · VEDIC

Match Birth Details

Endpoint POST https://starsapi.com/api/v3/vedic/matchmaking/match-birth-details

Returns the resolved birth context for both persons — parsed dates, weekday, location, timezone, and the ayanamsa applied to each birth moment. This is the couple version of /vedic/birth-details: every matchmaking endpoint accepts the same person1/person2 input shown here, and none of them echo birth input back — call this endpoint when you need to display or verify the interpreted input.

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:
namestringNoEchoed at the top of the person block.
genderstringNomale or female — determines bride/groom role assignment.
yearintegerYesBirth year.
monthintegerYesBirth month, 1–12.
dayintegerYesDay of month.
hourintegerYesHour, 24-hour.
minuteintegerYesMinute.
secondintegerNoDefault 0.
latitudenumberYesDecimal degrees.
longitudenumberYesDecimal degrees.
timezonestringYesIANA timezone.
placestringNoPlace label — echoed inside location when provided.
Optional (top-level):
ayanamsastringNoDefault lahiri. The resolved ayanamsa appears inside each person block.
node_typestringNomean (default) or true.

Response shape

person1 / person2

FieldTypeDescription
namestringEchoed when provided.
birth_detailsobjectdate, time, day (weekday), gender.
locationobjectlatitude, longitude, and place when provided.
timezonestringIANA timezone echoed.
ayanamsaobjectname, value, value_dms — computed for this person’s birth moment. Both persons use the same ayanamsa system; the value differs slightly because the birth dates differ.

Top-level

FieldTypeDescription
rolesobjectBride/groom role per person (gender-derived; defaults to person1 = bride).
node_typestringNode calculation in effect: mean or true.

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_GENDERGender not male/female/m/f.
405METHOD_NOT_ALLOWEDNon-POST request.

See also