SEARCH ASTRO INSIGHT API DOCS
The Rajju Dosha API evaluates Rajju Dosha compatibility factors according to Vedic astrology matchmaking principles, helping astrologers assess marital stability and long-term relationship prospects.
https://json.astroinsightapi.com/api/v1/match-making/rajju-dosha
en
hi
ma
Methodology and astrological context for Rajju Dosha.
The Rajju Dosha API is a Vedic astrology endpoint that detects and analyses Rajju Dosha — a significant affliction in Hindu marriage compatibility that arises when the Janma Nakshatras (birth stars) of two individuals fall within the same Rajju (rope) category. Rajju Dosha is considered one of the more serious doshas in match-making, as it is believed to adversely affect the longevity and well-being of the couple, particularly the husband, depending on the type of Rajju involved.
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 derives the Janma Nakshatra of each individual and maps them to their respective Rajju category. The 27 Nakshatras are traditionally grouped into five Rajju types — Siro (head), Kantha (neck), Udara (stomach), Kati (waist), and Pada (feet) — each associated with a different type of harm if both partners share the same Rajju. The API determines whether a Rajju Dosha exists, identifies the Rajju type, and assesses the nature and severity of the affliction.
The API returns a structured Rajju Dosha report that includes:
Nakshatra details for both individuals — the computed Janma Nakshatra for the male and female based on their birth data.
Rajju classification — the Rajju category assigned to each individual's Nakshatra.
Rajju Dosha status — whether a Rajju Dosha is present, i.e., whether both individuals share the same Rajju.
Rajju type and associated impact — the specific Rajju type (Siro, Kantha, Udara, Kati, or Pada) and the traditional interpretation of the harm associated with that Rajju if the dosha is present.
Cancellation or exception flags — any classical conditions under which the Rajju Dosha may be considered neutralised or reduced in severity.
Pre-marriage horoscope matching — the primary use case; used by astrologers and matrimonial platforms to identify Rajju Dosha as part of a comprehensive compatibility check before recommending a match.
Dosha severity assessment — used to distinguish between different levels of Rajju Dosha impact based on the specific Rajju type, enabling more nuanced match recommendations.
Multi-dosha compatibility pipelines — integrated into automated astrology engines that evaluate multiple doshas (Mangal, Vedha, Rajju, Nadi, etc.) in sequence.
Astrology SaaS and matrimonial platforms — powering Rajju Dosha detection within horoscope matching features for end users.
Jyotish (Vedic astrology) software — providing programmatic Rajju 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.
Maps each individual's Nakshatra to one of the five classical Rajju categories and checks for a shared Rajju, which constitutes the dosha.
Differentiates between Rajju types to convey the specific nature of the affliction, as each Rajju type carries a distinct traditional interpretation regarding its impact on the couple.
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 identify cases where the dosha is mitigated, providing a tradition-aligned and nuanced result.
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 Rajju Dosha.
The Rajju 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 Rajju 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 Rajju Dosha consumes 1 API credit. The endpoint delivers high performance with an average response time of ~67ms.
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.