SEARCH ASTRO INSIGHT API DOCS
The Papasamyam Details API evaluates Papasamyam compatibility factors in horoscope matching, helping identify potential marital harmony and challenges.
https://json.astroinsightapi.com/api/v1/match-making/papasamyam
en
hi
ma
Methodology and astrological context for Papasamyam Details.
The Papasamyam Details API is a Vedic astrology endpoint that performs a Papasamyam (also spelled Papashamya) analysis for two individuals being considered for marriage. Papasamyam is the process of evaluating and balancing the malefic planetary influences (Papa Grahas) present in the horoscopes of both individuals to determine whether their afflictions cancel each other out or create an imbalance.
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 positions of malefic planets (such as Mars, Saturn, Rahu, Ketu, the Sun, and the waning Moon) in both horoscopes and evaluates their placement across specific sensitive houses. It then computes the Papasamyam score or status for each individual and determines whether the two horoscopes are compatible from a Papasamyam perspective.
The API returns a detailed Papasamyam report that includes:
Papa (malefic) scores for both the male and female, indicating the total affliction level in each horoscope.
House-wise malefic planet placements — which malefic planets occupy which sensitive houses in each chart.
Papasamyam status — whether the two horoscopes are considered balanced (samya) or unbalanced, and whether the match is deemed compatible under this criterion.
Cancellation factors — any classical exceptions or neutralising conditions that may override or reduce the affliction, such as specific planetary combinations that cancel Mangal Dosha or similar doshas.
Pre-marriage horoscope matching — the primary use case; used by astrologers and matrimonial platforms to check whether a prospective couple's malefic planetary burdens are balanced before recommending a match.
Mangal Dosha and Dosha compatibility checks — identifying and comparing Mars affliction and other malefic influences as part of a broader compatibility workflow.
Astrology SaaS and matrimonial platforms — powering automated Papasamyam checks within horoscope matching engines for end users.
Jyotish (Vedic astrology) software — providing programmatic Papasamyam 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 planetary position calculations for each horoscope.
Evaluates malefic planet placements across the classical sensitive houses (typically the 1st, 2nd, 4th, 7th, 8th, and 12th houses) as defined in traditional Vedic astrology texts.
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 rules to identify cases where doshas are neutralised, providing a nuanced and tradition-aligned result rather than a simple binary output.
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 Papasamyam Details.
The Papasamyam 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.
The Papasamyam 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.
Each calculation request to Papasamyam Details consumes 1 API credit. The endpoint delivers high performance with an average response time of ~78ms.
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.