/api/astro/compatibility_match/1 creditPartner star search
A reverse lookup over a precomputed table of all 11,664 bride-and-groom star-and-pada combinations. Rather than scoring one couple, it answers the other question: given one person's birth star and pada, which stars and padas make a good match? Fix the groom's star to get the brides who suit him, or the bride's to get the grooms. Each row that comes back is `[star, pada, [the koota scores], score, [the supplementary tests]]`. Set `method` to anything containing 'south' to search the South Indian table instead of the North Indian one. Two behaviours will surprise you, so plan around them. `minimum_score` is compared against the Nadi column rather than the 36-point total, and Nadi is only ever 0 or 8; on top of that a `minimum_score` of 0 is treated as 'not supplied' and falls back to the default of 18 for North or 16 for South. The practical consequence is that the defaults return an empty list, and you need a value that is 8 or less and not 0 to get any rows at all. Likewise each of the four `advanced_checks` flags is read one column to the left of the test it names, so 'mahendra' filters on the total score and matches nothing, while 'vedha', 'rajju' and 'shree' filter on Mahendra, Vedha and Rajju respectively. To score a single couple instead, use /api/astro/ashtakoota/.
https://yogataraapi.prahlad.app/api/astro/compatibility_match/Authentication
Send your key in the X-API-Key header. Keys are server-side credentials — never put one in browser JavaScript or a mobile app.
X-API-Key: yt_live_a1b2c3d4_…
Content-Type: application/jsonRequest fields
| Field | Type | Required | Notes |
|---|---|---|---|
| boy_nakshatra | integer | required | |
| boy_paadham | integer | required | |
| girl_nakshatra | integer | required | |
| girl_paadham | integer | required | |
| method | string | required | NorthSouthCase-INSENSITIVE and matched by SUBSTRING: any value containing 'south' selects the South-Indian dataset (all_nak_pad_boy_girl_south.csv) with a default minimum_score of 16; anything else selects the North dataset with a default minimum_score of 18. Forwarded at. |
| minimum_score | integer | required | |
| advanced_checks | object | optional | mahendravedharajjushreeOBJECT whose KEYS are constrained (the values are booleans). Keys are matched case-insensitively (check.lower); any key outside this set is silently ignored. |
Example request
curl -X POST https://yogataraapi.prahlad.app/api/astro/compatibility_match/ \
-H "X-API-Key: $OCCULT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"boy_nakshatra":1,"boy_paadham":1,"girl_nakshatra":5,"girl_paadham":2,"method":"South","minimum_score":0,"advanced_checks":{"mahendra":true,"vedha":true,"rajju":true,"shree":true}}'Response
{
"data": {
"compatibility_matcher": []
},
"message": "successful",
"is_error": false
}Captured from a real call using the exact request above. Results sit under data.
Errors
Metering errors return { "error": "…", "message": "<code>", "is_error": true }. Show error to people and branch on message. See the error reference.