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
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
person1
object
Yes
First person’s birth data (see fields below).
person2
object
Yes
Second person’s birth data (same fields).
Each person object:
name
string
No
Echoed at the top of the person block.
gender
string
No
male or female — determines bride/groom role assignment.
year
integer
Yes
Birth year.
month
integer
Yes
Birth month, 1–12.
day
integer
Yes
Day of month.
hour
integer
Yes
Hour, 24-hour.
minute
integer
Yes
Minute.
second
integer
No
Default 0.
latitude
number
Yes
Decimal degrees.
longitude
number
Yes
Decimal degrees.
timezone
string
Yes
IANA timezone.
place
string
No
Place label — echoed inside location when provided.
Optional (top-level):
ayanamsa
string
No
Default lahiri. The resolved ayanamsa appears inside each person block.
node_type
string
No
mean (default) or true.
Response shape
person1 / person2
Field
Type
Description
name
string
Echoed when provided.
birth_details
object
date, time, day (weekday), gender.
location
object
latitude, longitude, and place when provided.
timezone
string
IANA timezone echoed.
ayanamsa
object
name, 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
Field
Type
Description
roles
object
Bride/groom role per person (gender-derived; defaults to person1 = bride).