SEARCH ASTRO INSIGHT API DOCS
The Match Planet Details Extended API delivers enhanced planetary compatibility analysis with detailed astrological calculations for advanced matchmaking systems.
https://json.astroinsightapi.com/api/v1/match-making/planet-details/extended
en
hi
ma
Methodology and astrological context for Match Planet Details Extended.
The Match Planet Details Extended API returns an enriched, extended planetary data set for both individuals in a Kundali Milan (horoscope matching) workflow. It is the comprehensive superset of the Match Planet Details endpoint, augmenting the standard planet-by-planet positional data with deeper astrological attributes — including planetary strength indicators, divisional chart positions, special planetary conditions, and additional compatibility-relevant metrics — that are required for the most thorough and nuanced matchmaking analysis.
The API accepts complete birth date, time, and geographic coordinates for both the male and female, computes their full extended planetary profiles using the specified Ayanamsha, and returns a richly detailed, comparison-ready planetary data set for each individual.
What data it returns
Main use cases
Key functionality
X-Ayanamsha header, ensuring all calculations are aligned with the preferred Jyotish traditionAccept-Language header, making the API suitable for regional and multilingual matrimonial and astrology platformsPayload specifications for JSON request body.
| 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
|
| 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 |
Explore complementary endpoints in this category.
Comprehensive developer guidance for Match Planet Details Extended.
The Match Planet Details Extended 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.
The Match Planet Details Extended 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.
Each calculation request to Match Planet Details Extended consumes 1 API credit. The endpoint delivers high performance with an average response time of ~68ms.
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)).
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.
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.
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.