SEARCH ASTRO INSIGHT API DOCS
The Match Dashakoot Points API calculates Dashakoot compatibility scores, providing additional relationship matching insights beyond traditional Ashtakoot analysis.
https://json.astroinsightapi.com/api/v1/match-making/dashakoot/points
en
hi
ma
Methodology and astrological context for Match Dashakoot Points.
The Match Dashakoot Points API is a Vedic astrology compatibility scoring endpoint that calculates the Dashakoot (also known as Ashtakoot) matching score between two individuals based on their birth details. It is a core component of traditional Hindu marriage compatibility analysis.
This API accepts the complete birth details of two individuals — a male and a female — including their date, time, and geographic coordinates of birth, and computes the Dashakoot compatibility score. Internally, it derives the natal Moon positions for both individuals using the specified Ayanamsha system and evaluates compatibility across the eight (or ten, in the Dashakoot system) classical Koot (attribute) categories defined in Vedic astrology.
The API returns a structured compatibility report that includes:
Individual Koot scores — the points awarded for each of the Koot categories (such as Varna, Vashya, Tara, Yoni, Graha Maitri, Gana, Bhakoot, and Nadi, among others depending on the system).
Total compatibility score — the aggregate points out of the maximum possible score, indicating the overall compatibility level between the two individuals.
Koot-level details — descriptive information for each category, including the matched values for both individuals and the resulting score.
Marriage compatibility analysis — the primary use case; used by astrologers and matrimonial platforms to assess the suitability of a match between two prospective partners.
Relationship counselling tools — integration into apps or platforms that provide Vedic astrology-based relationship insights.
Astrology SaaS platforms — powering automated horoscope matching features for end users.
Jyotish (Vedic astrology) software — backend computation for desktop or web-based astrology applications that need programmatic Dashakoot scoring.
Accepts precise birth data (day, month, year, hour, minute, second, latitude, longitude, and timezone offset) for both individuals independently, allowing accurate Moon sign and Nakshatra derivation.
Supports configurable Ayanamsha systems (e.g., Lahiri, Raman, KP) via the X-Ayanamsha header, enabling compatibility with different schools of Vedic astrology.
Supports multi-language responses via the Accept-Language header, making it suitable for localised applications.
Computes results based on the classical Dashakoot framework, ensuring alignment with traditional Vedic matching methodology.
Payload 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 Dashakoot Points.
The Match Dashakoot Points 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 Dashakoot Points 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 Dashakoot Points consumes 1 API credit. The endpoint delivers high performance with an average response time of ~79ms.
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.