Building a Matrimonial Platform
This guide covers integrating Asterwise into a matrimonial platform — from profile creation through compatibility scoring.
Overview
A complete matrimonial astrology flow involves three steps:
- Collect birth details from both profiles
- Geocode city names to coordinates
- Run compatibility scoring
Step 1 — Geocode birth cities
Most users enter city names, not coordinates. Use the Geocode endpoint to resolve them:
curl -X GET \
"https://api.asterwise.com/v1/utils/geocode?q=Mumbai&limit=1" \
-H "Authorization: Bearer YOUR_API_KEY"
The response gives you latitude, longitude, and timezone — all
three are required for the chart endpoints.
Step 2 — Run Ashtakoota matchmaking
The core North Indian compatibility score out of 36 points:
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",
"lat": 19.0760,
"lon": 72.8777,
"timezone": "Asia/Kolkata"
},
"person2": {
"date": "1990-06-21",
"time": "15:30",
"lat": 41.9028,
"lon": 12.4964,
"timezone": "Europe/Rome"
}
}'
Always check Rajju and Vedha first
Before displaying the score, check rajju_dosha and vedha_dosha.
When either is true, the classical tradition treats the match as
incompatible regardless of the total Guna score.
Step 3 — Run additional checks
For South Indian platforms, also run:
- Dashakoot — 10-point Tamil system
- Papa Samyam — malefic balance
- Porutham — Tamil 10-porutham
- Thirumana Porutham — Tamil 12-porutham
Recommended endpoint sequence
| Step | Endpoint | Purpose |
|---|---|---|
| 1 | GET /v1/utils/geocode | Resolve city names |
| 2 | POST /v1/astro/matchmaking | Ashtakoota score + vetoes |
| 3 | POST /v1/astro/matchmaking/papasamyam | Malefic balance |
| 4 | POST /v1/astro/matchmaking/porutham | Tamil system (optional) |