POST/v1/astro/matchmaking

Kundali Milan — Matchmaking

Complete Vedic compatibility analysis using Ashtakoot Guna Milan (36-point system). Returns all 8 koota scores, Mangal Dosha compatibility with Dosha Samya analysis, classical veto checks (Vedha and Rajju Dosha), supplementary checks (Mahendra, Stree Deergha), and compatibility narrative with strengths, concerns, and recommendation. Also known as Kundali Milan, Gun Milan, or Ashtakoot Milan. Calculates 36-point compatibility score with Rajju, Vedha, and Dosha Samya classical rules.

Request parameters

person1required

object

person1.locationoptional

string | null

City name to resolve to lat/lon/tz automatically. Example: 'Mumbai' or 'New Delhi, India'. If provided, latitude, longitude and timezone are not required.

person1.nameoptional

string

Person name associated with the birth record

person1.daterequired

string

Birth date in YYYY-MM-DD format

person1.timeoptional

string | null

Birth time in HH:MM 24-hour format. If omitted, sunrise chart is used as fallback.

person1.latitudeoptional

number | null

Latitude. Required if location not provided.

person1.longitudeoptional

number | null

Longitude. Required if location not provided.

person1.timezoneoptional

string | null

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.

person1.utc_offsetoptional

string | null

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.

person1.ayanamsaoptional

string

Sidereal ayanamsa mode used in calculations

person2required

object

person2.locationoptional

string | null

City name to resolve to lat/lon/tz automatically. Example: 'Mumbai' or 'New Delhi, India'. If provided, latitude, longitude and timezone are not required.

person2.nameoptional

string

Person name associated with the birth record

person2.daterequired

string

Birth date in YYYY-MM-DD format

person2.timeoptional

string | null

Birth time in HH:MM 24-hour format. If omitted, sunrise chart is used as fallback.

person2.latitudeoptional

number | null

Latitude. Required if location not provided.

person2.longitudeoptional

number | null

Longitude. Required if location not provided.

person2.timezoneoptional

string | null

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.

person2.utc_offsetoptional

string | null

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.

person2.ayanamsaoptional

string

Sidereal ayanamsa mode used in calculations

Response fields

success

boolean

True if the request succeeded

message

string

Human-readable status message

data

object

data.total_score

number

Overall Guna Milan score out of 36

data.breakdown

object

Per-koota score breakdown

data.compatibility_level

string

Textual compatibility band derived from score

data.doshas

object

Detected compatibility doshas

data.dosha_cancellations

object

Traditional dosha cancellation flags

data.analysis

object

Additional high-level matchmaking analysis details

data.classical_vetoes

object | null

Classical veto checks (Vedha, Rajju) and veto status

data.mangal_compatibility

object | null

Mangal Dosha compatibility assessment between both partners

data.supplementary_checks

object | null

Supplementary classical checks: Mahendra, Vedha, Rajju

data.compatibility_narrative

object | null

Narrative compatibility summary with strengths and concerns

data.birth_time_provided

boolean

Whether a precise birth time was provided for both persons. False when either person's birth time was not supplied or treated as unknown.

Errors

api_key_invalid

Invalid API key format.

api_key_missing

API key is missing. Include it in the Authorization header as 'Bearer YOUR_KEY'.

api_key_not_found

The provided API key was not found. Verify the key in your Asterwise dashboard.

api_key_revoked

This API key has been revoked.

burst_limit_exceeded

Too many requests per minute. Please slow down.

internal_error

Something went wrong on our end. Please try again, or contact [email protected] if the problem persists. Include your request_id when contacting support.

ip_rate_limit_exceeded

Too many requests from this IP address. Please slow down.

monthly_usage_limit_exceeded

Monthly API call limit reached. Upgrade your plan to continue.

payload_too_large

Request body exceeds maximum allowed size of 64KB.

subscription_expired

Your subscription has expired. Please renew at asterwise.com/dashboard to continue.

validation_error

The request couldn't be processed. See the 'details' field for specific field-level issues.

Related endpoints

• Dashakoot — 10-Koota Compatibility
• Kerala Porutham — 10-Porutham Compatibility
• Papasamyam — Malefic Planet Compatibility
• Thirumana Porutham (12 Poruthams)

Request

POST·application/json

curl

curl -X POST "https://api.asterwise.com/v1/astro/matchmaking" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"person1":{"date":"1985-11-12","time":"06:45","latitude":19.076,"longitude":72.8777,"timezone":"Asia/Kolkata"},"person2":{"date":"1988-03-24","time":"14:30","latitude":28.6139,"longitude":77.209,"timezone":"Asia/Kolkata"}}'

Python

import asterwise
from asterwise.api.astrology_api import AstrologyApi
from asterwise.models.matchmaking_request import MatchmakingRequest

configuration = asterwise.Configuration(
    host="https://api.asterwise.com",
    access_token="YOUR_API_KEY",
)

request = MatchmakingRequest(
    person1={'date': '1985-11-12', 'time': '06:45', 'latitude': 19.076, 'longitude': 72.8777, 'timezone': 'Asia/Kolkata'},
    person2={'date': '1988-03-24', 'time': '14:30', 'latitude': 28.6139, 'longitude': 77.209, 'timezone': 'Asia/Kolkata'},
)

with asterwise.ApiClient(configuration) as client:
    api = AstrologyApi(client)
    result = api.matchmaking(matchmaking_request=request)
    print(result)

TypeScript

import { createClient, createConfig, matchmaking } from 'asterwise';

const client = createClient(createConfig({
  baseUrl: 'https://api.asterwise.com',
  headers: { Authorization: 'Bearer YOUR_API_KEY' },
}));

const result = await matchmaking({
  client,
  body: {
      "person1": {
        "date": "1985-11-12",
        "time": "06:45",
        "latitude": 19.076,
        "longitude": 72.8777,
        "timezone": "Asia/Kolkata"
      },
      "person2": {
        "date": "1988-03-24",
        "time": "14:30",
        "latitude": 28.6139,
        "longitude": 77.209,
        "timezone": "Asia/Kolkata"
      }
  },
});

console.log(result.data);

Response

200 OK·application/jsonsigned

{
  "success": true,
  "message": "success",
  "data": {
    "total_score": 27.0,
    "breakdown": {
      "Varna": 1.0,
      "Vashya": 2.0,
      "Tara": 3.0,
      "Yoni": 2.0,
      "GrahaMaitri": 5.0,
      "Gana": 6.0,
      "Bhakoot": 0.0,
      "Nadi": 8.0
    },
    "compatibility_level": "Very Good",
    "doshas": {
      "bhakoot_dosha": true,
      "bhakoot_dosha_type": "Nav-Pancham"
    },
    "dosha_cancellations": {
      "bhakoot_dosha_cancelled": true
    },
    "analysis": {
      "major_doshas": 1,
      "cancelled_doshas": 1,
      "recommendation": "This match is recommended by classical Jyotish standards."
    },
    "classical_vetoes": {
      "has_veto": false,
      "vedha": {
        "present": false,
        "description": "No Vedha — Nakshatras are not mutually obstructive."
      },
      "rajju": {
        "present": false,
        "description": "Different Rajju groups — no dosha from Rajju.",
        "rajju_type": null
      },
      "veto_note": "No classical veto conditions present."
    },
    "mangal_compatibility": {
      "person_a_manglik": true,
      "person_a_severity": "medium",
      "person_a_cancellations": [],
      "person_b_manglik": false,
      "person_b_severity": null,
      "person_b_cancellations": [
        "Jupiter aspects or conjoins Mars"
      ],
      "match_status": "mismatch",
      "description": "One partner is Manglik (Mars in the 1st or 12th house — medium severity). Traditional concern — remedial measures are ad…"
    },
    "supplementary_checks": {
      "mahendra": {
        "is_auspicious": false,
        "distance": 11,
        "description": "Mahendra is not favorable — no major harm, but this factor is neutral."
      },
      "stree_deergha": {
        "distance": 11,
        "quality": "average",
        "is_favorable": false,
        "description": "Stree Deergha count is 11 (9-15 inclusive) — average. The bride's wellbeing is moderately supported."
      }
    },
    "compatibility_narrative": {
      "overall": "Good compatibility with a Guna Milan score of 27.0/36. The match has solid foundations with some areas that benefit from…",
      "strengths": [
        "Nadi Koota perfect (8/8) — constitutional and genetic compatibility is excellent. No health conflicts indicated.",
        "Gana Koota perfect (6/6) — temperaments and behavioral patterns are fully compatible.",
        "... and 4 more items"
      ],
      "concerns": [],
      "recommendation": "This match is recommended by classical Jyotish standards."
    },
    "birth_time_provided": true
  }
}