Logo

SEARCH ASTRO INSIGHT API DOCS

Home Vedic Astrology
POST Vedic API v1

Match Birth Details

The Match Birth Details API provides essential birth information required for horoscope matching and compatibility analysis between two individuals.

https://json.astroinsightapi.com/api/v1/match-making/birth-details
Credit Cost
1 Credit
Avg Latency
~30ms
Auth Type
Basic Auth
Format
JSON / UTF-8

Available Response Languages

🇬🇧 English en
🇮🇳 Hindi hi
🇮🇳 Marathi ma

API Overview & Calculation Details

Methodology and astrological context for Match Birth Details.

The Match Birth Details API computes and returns the core Vedic astrological birth details for two individuals — a male and a female — as the foundational step in a Kundali Milan (horoscope matching) workflow. In Vedic astrology, marriage compatibility analysis begins with deriving each person's key astrological identifiers from their birth data: their Rashi (Moon sign), Nakshatra (lunar mansion), Ascendant (Lagna), and related chart parameters. This endpoint performs those calculations for both individuals simultaneously, providing the essential astrological profile data that underpins all subsequent matchmaking analysis.

The API accepts complete birth date, time, and geographic coordinates for both the male and female, calculates their respective astrological birth details using the specified Ayanamsha, and returns a structured profile for each individual ready for use in compatibility scoring and report generation.


What data it returns

  • For each individual (male and female): their computed Rashi (Moon sign), Janma Nakshatra (birth lunar mansion), Nakshatra pada, and Ascendant (Lagna) sign
  • Nakshatra lord and Rashi lord for each individual, establishing the planetary rulers governing their core astrological identity
  • Charan (pada) details of the Janma Nakshatra, providing the granular lunar mansion subdivision used in compatibility calculations
  • Moon's degree and sign position for each individual, which forms the basis of Ashtakoot and other matching systems
  • Additional birth chart identifiers relevant to the matchmaking process, such as Gana (temperament group), Varna (spiritual class), Yoni (instinctive nature), and Nadi (energy channel) — the key Koota attributes derived from the Nakshatra
  • Localised output based on the requested language

Main use cases

  • Kundali Milan initiation — Serving as the first API call in a horoscope matching workflow, establishing the astrological birth profiles of both individuals before compatibility scoring endpoints are invoked
  • Marriage compatibility platforms — Powering the birth detail computation layer of matrimonial and matchmaking applications that offer Vedic astrology-based compatibility analysis
  • Astrological profile generation — Providing a quick, dual-individual birth detail lookup for practitioners or platforms that need both partners' core astrological identifiers in a single request
  • Koota-based matching preparation — Supplying the Nakshatra-derived Koota attributes (Gana, Varna, Yoni, Nadi, etc.) needed as inputs for Ashtakoot or Dashakoot compatibility scoring
  • Compatibility report enrichment — Embedding individual birth detail summaries as introductory sections within comprehensive Kundali Milan reports, contextualising the match analysis for end users
  • Multi-step matchmaking workflows — Acting as the data-gathering step that feeds into subsequent match-making endpoints for detailed compatibility scores, dosha analysis, and remedial guidance

Key functionality

  • Dual-individual calculation — Accepts and processes birth data for both the male and female in a single request, computing each person's full astrological birth profile simultaneously and returning both in one response
  • Nakshatra and Koota attribute derivation — Computes not just the Nakshatra but also the Koota attributes (Gana, Varna, Yoni, Nadi, and others) directly from the Nakshatra, providing all the building blocks needed for Ashtakoot compatibility scoring
  • Ascendant and Moon sign precision — Calculates both the Lagna and the Moon's Rashi and degree position with geographic and timezone accuracy, ensuring the birth profiles are correctly grounded in each individual's local birth coordinates
  • Configurable Ayanamsha — Supports multiple Ayanamsha settings (e.g., Lahiri, Raman, KP) via the X-Ayanamsha header, ensuring sidereal calculations are aligned with the preferred Jyotish tradition
  • Geographic precision — Accepts separate latitude, longitude, and timezone values for each individual, correctly handling cases where the two individuals were born in different locations or time zones
  • Multi-language support — Responses can be localised via the Accept-Language header, making the API suitable for regional and multilingual matrimonial and astrology platforms
  • Matchmaking suite entry point — Designed as the foundational endpoint of the AstroInsight matchmaking suite, with its output serving as the input context for compatibility scoring, Mangal Dosha analysis, and other match-making endpoints

Request Parameters

Payload specifications for JSON request body.

application/json
Parameter Type Description & Example
m_day
Required
integer
Male day of birth (1–31).
Example: 15
m_month
Required
integer
Male month of birth (1–12).
Example: 9
m_year
Required
integer
Male year of birth (e.g., 1994).
Example: 1994
m_hour
Required
integer
Male hour of birth in 24-hour format (0–23).
Example: 12
m_min
Required
integer
Male minute of birth (0–59).
Example: 30
m_sec
Optional
integer
Male second of birth (0–59). Optional. If not provided, it is considered as 0.
Example: 0
m_lat
Required
float
Male birth location latitude.
Example: 28.6139
m_lon
Required
float
Male birth location longitude.
Example: 77.1025
m_tzone
Optional
float
Male timezone offset from UTC. Optional. If not provided, it is considered as 5.5 (IST).
Example: 5.5
f_day
Required
integer
Female day of birth (1–31).
Example: 15
f_month
Required
integer
Female month of birth (1–12).
Example: 7
f_year
Required
integer
Female year of birth (e.g., 1995).
Example: 1995
f_hour
Required
integer
Female hour of birth in 24-hour format (0–23).
Example: 12
f_min
Required
integer
Female minute of birth (0–59).
Example: 30
f_sec
Optional
integer
Female second of birth (0–59). Optional. If not provided, it is considered as 0.
Example: 0
f_lat
Required
float
Female birth location latitude.
Example: 28.6139
f_lon
Required
float
Female birth location longitude.
Example: 77.1025
f_tzone
Optional
float
Female timezone offset from UTC. Optional. If not provided, it is considered as 5.5 (IST).
Example: 5.5

Required & Optional Headers

Header Key Value / Format Description
Authorization
Required
Basic {base64} Base64 encoded string of CLIENT_ID:CLIENT_SECRET.
Content-Type
Required
application/json Specifies JSON payload format in request body.
Accept-Language
Optional
en, hi, ta, te... Returns localized astrology output. Default: en
X-Ayanamsha
Optional
lahiri, raman, krishnamurti... Ayanamsha system: lahiri, raman, fagan_bradley, usha_shashi, krishnamurti, djwhal_khul, yukteshwar, jn_bhasin, suryasiddhanta, aryabhata. Default: lahiri

Frequently Asked Questions

Comprehensive developer guidance for Match Birth Details.

What is the Match Birth Details API and what data does it provide?

The Match Birth Details API provides authentic Match Making calculations based on Vedic astrology algorithms. It returns structured JSON data containing detailed planetary positions, house calculations, and astrological parameters suitable for Kundli apps, astrology websites, and developer applications.

What input parameters are required to call Match Birth Details?

The Match Birth Details API requires standard Vedic birth details: day, month, year, hour, min, sec, latitude (lat), longitude (lon), and timezone (tzone). All parameters can be passed in the JSON request body.

How many credits does the Match Birth Details endpoint consume?

Each calculation request to Match Birth Details consumes 1 API credit. The endpoint delivers high performance with an average response time of ~30ms.

How do I authenticate with the Match Birth Details API?

Authenticate using HTTP Basic Authentication by including your Base64 encoded client_id:client_secret credentials in the Authorization header (Authorization: Basic BASE64(client_id:client_secret)).

Can I get Match Birth Details responses in regional Indian languages?

Yes! The API supports multiple languages including English, Hindi, Marathi. Pass your desired language code (e.g. 'hi' for Hindi, 'ta' for Tamil, 'en' for English) in the Accept-Language request header.

Which Ayanamsha systems can be calculated with Match Birth Details?

Supported Ayanamshas include NC Lahiri (Default), BV Raman, Krishnamurti (KP), Fagan Bradley, Usha Shashi, Djwhal Khul, Sri Yukteshwar, JN Bhasin, Surya Siddhanta, and Aryabhata. Specify your choice using the X-Ayanamsha header.

What response format and HTTP codes does this API return?

The API returns clean JSON UTF-8 output. Successful requests return HTTP 200 OK with the computed data payload. Parameter validation errors return HTTP 422 with actionable error messages.

POST match-making/birth-details
Presets:
Live Output
Click Send above to execute calculation.
Sample Output

API Categories