---
title: "Papasamyam — Malefic Planet Compatibility"
method: POST
path: "/v1/astro/matchmaking/papasamyam"
tags: ["Astrology"]
---

# Papasamyam — Malefic Planet Compatibility

`POST /v1/astro/matchmaking/papasamyam`

## Request

- Base URL: `https://api.asterwise.com`
- URL: `https://api.asterwise.com/v1/astro/matchmaking/papasamyam`
- Auth: HTTP bearer

Computes Papasamyam, the malefic-planet compatibility check, between two natal charts. Scores each person based on Sun, Mars, Saturn, Rahu, Ketu in houses 1, 2, 4, 7, 8, 12 from Lagna, Moon, and Venus (#105). Compatible if score difference ≤ 11. person1 = groom, person2 = bride.

## Request body

- PapasamyamRequest
  - `person1` BirthInput, required
    - `location` string, nullable: City name to resolve to lat/lon/tz automatically. Example: 'Mumbai' or 'New Delhi, India'. If provided, latitude, longitude and timezone are not required.
    - `name` string: Person name associated with the birth record
    - `date` string, required: Birth date in YYYY-MM-DD format
    - `time` string, nullable: Birth time in HH:MM 24-hour format. If omitted, sunrise chart is used as fallback.
    - `latitude` number, nullable: Latitude. Required if location not provided.
    - `longitude` number, nullable: Longitude. Required if location not provided.
    - `timezone` string, nullable: IANA timezone. Required if location not provided (unless utc_offset is given). For dates before the zone adopted a standard time, the birthplace's local mean time (longitude / 15 hours) is used.
    - `utc_offset` string, nullable: Optional explicit UTC offset of the birth time, as ±HH:MM or ±HH:MM:SS (e.g. '+04:51:31' for Bombay mean time). Overrides the offset `timezone` would give. Use it when the birth record states the offset, or for historical local times the IANA database cannot represent.
    - `ayanamsa` 'lahiri' | 'raman' | 'kp' | 'tropical': Sidereal ayanamsa mode used in calculations
  - `person2` BirthInput, required
    - `location` string, nullable: City name to resolve to lat/lon/tz automatically. Example: 'Mumbai' or 'New Delhi, India'. If provided, latitude, longitude and timezone are not required.
    - `name` string: Person name associated with the birth record
    - `date` string, required: Birth date in YYYY-MM-DD format
    - `time` string, nullable: Birth time in HH:MM 24-hour format. If omitted, sunrise chart is used as fallback.
    - `latitude` number, nullable: Latitude. Required if location not provided.
    - `longitude` number, nullable: Longitude. Required if location not provided.
    - `timezone` string, nullable: IANA timezone. Required if location not provided (unless utc_offset is given). For dates before the zone adopted a standard time, the birthplace's local mean time (longitude / 15 hours) is used.
    - `utc_offset` string, nullable: Optional explicit UTC offset of the birth time, as ±HH:MM or ±HH:MM:SS (e.g. '+04:51:31' for Bombay mean time). Overrides the offset `timezone` would give. Use it when the birth record states the offset, or for historical local times the IANA database cannot represent.
    - `ayanamsa` 'lahiri' | 'raman' | 'kp' | 'tropical': Sidereal ayanamsa mode used in calculations

## Response `200`

Successful Response

- ApiResponsePapasamyamResponse
  - `success` boolean: True if the request succeeded
  - `message` string: Human-readable status message
  - `data` PapasamyamResponse, required
    - `birth_time_provided` boolean: True only when both people supplied a birth time. See person1_birth_time_provided and person2_birth_time_provided.
    - `person1_birth_time_provided` boolean: True when person 1 supplied a birth time.
    - `person2_birth_time_provided` boolean: True when person 2 supplied a birth time.
    - `person1` object, required
    - `person2` object, required
    - `score_difference` number, required
    - `compatible` boolean, required
    - `compatibility_level` string, required
    - `imbalance` string, nullable: Balanced, Groom heavier or Bride heavier. Bride heavier is never compatible.
    - `threshold` number, required: How far the bride's score may exceed the groom's (0: not at all).

## Other responses

- `401`: Authentication failed
- `403`: Authorization failed
- `404`: Resource not found
- `413`: Payload too large
- `422`: Validation error
- `429`: Rate limit exceeded
- `500`: Internal error
- `502`: Upstream provider error
- `503`: Service unavailable

## Changes

- **2026-10-19** `3c4bbb1194e2`: 1 info
  - added the optional property `data/imbalance` to the response with the `200` status

[Operation history](https://skmtc.dev/asterwise/apis/asterwise-api/changes/v1/astro/matchmaking/papasamyam/post.md)

---

[API](https://skmtc.dev/asterwise/apis/asterwise-api.md) · [All operations](https://skmtc.dev/asterwise/apis/asterwise-api/llms.txt) · [OpenAPI document](https://skmtc.dev/asterwise/apis/asterwise-api/revisions/e77850f7c569?raw)