What the endpoint returns
POST /v1/astro/matchmaking takes two births and returns total_score out of 36, a breakdown with the eight kootas (Varna, Vashya, Tara, Yoni, Graha Maitri, Gana, Bhakoot, Nadi), the Bhakoot and Nadi dosha flags with their cancellations, mangal_compatibility for both people, and classical_vetoes with rajju and vedha as explicit checks and a top-level has_veto.
Request
curl -X POST https://api.asterwise.com/v1/astro/matchmaking \
-H "Authorization: Bearer $ASTERWISE_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"}}'
Response, abbreviated
{
"success": true,
"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 },
"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 }
}
}
}
Every field is documented in the Kundali Milan reference, including supplementary_checks (Mahendra, Stree Deergha) and compatibility_narrative.
Why vetoes are separate from the score
Classical texts treat Rajju and Vedha as conditions checked before the Guna count, not as penalties inside it. A 30/36 match with a Rajju dosha is still a rejected match, and a matrimony product needs to show that as a veto, not a slightly lower number. The architecture and the sources are in Rajju and Vedha as hard vetoes.
Regional systems
| System | Endpoint | Reference |
|---|---|---|
| Ashtakoot Guna Milan (North Indian, 36 points) | POST /v1/astro/matchmaking | docs |
| Dashakoot (10 kootas) | POST /v1/astro/matchmaking/dashakoot | docs |
| Kerala Porutham (10 poruthams) | POST /v1/astro/matchmaking/porutham | docs |
| Tamil Thirumana Porutham | POST /v1/astro/matchmaking/thirumana-porutham | docs |
| Papasamyam (malefic balance) | POST /v1/astro/matchmaking/papasamyam | docs |
Build it
The matrimonial platform guide covers profile birth data through scoring. Add Vedic matchmaking to a Next.js app in 30 minutes is a working repo with one server action and no key in the browser. The comparison pages show which other providers document Rajju and Vedha at all.
Start with 500 free calls a month, no card, no expiry. Every plan includes all 118 endpoints. See pricing or create a key.