SEARCH ASTRO INSIGHT API DOCS
The Vedha Dosha API analyzes Vedha Dosha conditions in horoscope matching and provides insights into their potential impact on relationships and marriage compatibility.
https://json.astroinsightapi.com/api/v1/match-making/vedha-dosha
en
hi
ma
Methodology and astrological context for Vedha Dosha.
The Vedha Dosha API is a Vedic astrology endpoint that detects and analyses Vedha Dosha — a specific affliction or obstruction arising from the mutual interference of Nakshatras (lunar mansions) in the horoscopes of two individuals being considered for marriage. Vedha Dosha is evaluated as part of the Tara Koot compatibility check and can nullify an otherwise favourable match if present.
This API accepts the complete birth details of two individuals — a male and a female — including their date, time, and geographic coordinates of birth. It calculates the Janma Nakshatra (birth star) of each individual and checks whether the Nakshatras of the two individuals stand in a Vedha (obstructive) relationship to each other according to classical Vedic astrology rules. Certain pairs of Nakshatras are considered mutually Vedha, meaning their combination is believed to create obstacles, conflict, or harm in the relationship. The API identifies whether such a Vedha relationship exists and provides the relevant details.
The API returns a structured Vedha Dosha report that includes:
Nakshatra details for both individuals — the computed Janma Nakshatra (and Pada, if applicable) for the male and female based on their birth data.
Vedha Dosha status — whether a Vedha Dosha is present between the two Nakshatras, along with the specific Vedha pair identified.
Dosha severity or impact — an indication of the strength or significance of the Vedha, where applicable.
Cancellation or exception flags — classical conditions under which the Vedha Dosha may be considered neutralised or overridden, as defined in traditional Jyotish texts.
Marriage compatibility screening — the primary use case; used by astrologers and matrimonial platforms to flag Vedha Dosha as part of a comprehensive horoscope matching workflow.
Tara Koot analysis — used as a sub-component within the broader Ashtakoot or Dashakoot matching system to refine compatibility scoring.
Dosha detection pipelines — integrated into automated astrology engines that check multiple doshas (Mangal, Vedha, Nadi, etc.) in sequence before recommending a match.
Astrology SaaS and matrimonial platforms — powering Vedha Dosha checks within horoscope matching features for end users.
Jyotish (Vedic astrology) software — providing programmatic Vedha Dosha computation for desktop or web-based astrology applications.
Accepts precise birth data (day, month, year, hour, minute, second, latitude, longitude, and timezone offset) for both individuals independently, enabling accurate Nakshatra derivation for each horoscope.
Evaluates Vedha relationships using the classical list of mutually obstructive Nakshatra pairs as defined in traditional Vedic astrology literature.
Supports configurable Ayanamsha systems (e.g., Lahiri, Raman, KP) via the X-Ayanamsha header, ensuring compatibility with different schools of Vedic astrology.
Supports multi-language responses via the Accept-Language header, making it suitable for localised and regional applications.
Applies classical exception and cancellation rules to provide a nuanced result, distinguishing between active Vedha Dosha and cases where the dosha is considered mitigated.
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 Vedha Dosha.
The Vedha Dosha 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 Vedha Dosha 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 Vedha Dosha consumes 1 API credit. The endpoint delivers high performance with an average response time of ~84ms.
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.