DEV Community

Amrita Singh
Amrita Singh

Posted on

How Matrimony Platforms Are Using Astrology APIs to Improve Match Quality

In India, the question "what's your kundali score" still gets asked across millions of marriage conversations every year. It is not a fringe ritual. For roughly 80% of Indian families involved in arranged or semi-arranged marriages, kundali matching is a non-negotiable step before two families seriously discuss compatibility. The Indian matrimony market is a multi-billion-dollar industry, and the platforms that have scaled inside it have done so partly by automating a process that used to require a personal visit to a family astrologer, a 45-minute consultation, and a hand-drawn report.

That automation is happening through astrology APIs. And it is changing what matrimony platforms can offer, what they can charge for, and how fast they can move users from a profile view to a compatibility verdict.

A 2,000-year-old algorithm, now an API call
Kundali matching is not new. The Ashtakoot system, the most widely used compatibility framework in North and East Indian Vedic tradition, has been documented for centuries. It evaluates two birth charts across eight Kootas (factors) and produces a score out of 36, with 18 typically considered the minimum acceptable threshold for marriage. South Indian families often layer in Dashakoot, a 10-Koot system, on top. Both rely on the same underlying inputs: full birth date, time, location, and gender for both partners.

What has changed is that this calculation no longer needs a human astrologer in the loop for every match. The math is deterministic. Given two correctly captured birth profiles, an Ashtakoot or Dashakoot score is computable in milliseconds. The interpretation layer (which factors carry which weight, what counts as a high or low compatibility per Koot, when a Mangal Dosha cancels out) is well-codified. This is exactly the kind of problem APIs are good at solving.

From astrologer's office to API endpoint

Three years ago, the dominant model on Indian matrimony platforms was either to skip kundali matching entirely (limiting reach to families who didn't insist on it), to ask users to upload PDF kundalis from their own astrologers (slow, inconsistent, hard to standardise), or to maintain in-house astrologer panels (expensive, doesn't scale beyond a certain volume). Each had ceiling effects.

The shift has been to integrate dedicated Vedic astrology APIs that handle the calculations natively, return structured data in JSON, and support the full set of compatibility checks Indian users expect. The platforms that have done this well now offer kundali matching as a baseline feature on free tiers and reserve detailed report generation, multilingual outputs, and astrologer-reviewed interpretations for premium subscriptions.
It is the classic API-as-leverage story: a feature that took 45 minutes per couple now happens in under a second per couple, with no marginal cost beyond the API call.

What a modern Kundali Matching API actually delivers

For matrimony product teams evaluating this category, the relevant capabilities to look for cluster into four buckets:
Ashtakoot Milan (36-point Guna Milan). The core compatibility score across the eight Kootas: Varna, Vashya, Tara, Yoni, Graha Maitri, Gana, Bhakoot, Nadi. A good API returns the score per Koot, the maximum points per Koot, an interpretation paragraph for each, and the aggregate out of 36.

*Dashakoot Milan *
The 10-Koot variant used predominantly in South Indian and parts of Western Indian matchmaking. Some matrimony platforms surface only Ashtakoot to keep the UX simple, others let users toggle between systems based on regional preference.
Mangal Dosha (Manglik) analysis. Whether either partner is Manglik, what severity, whether the dosha is cancelled by other planetary positions, and whether the two charts neutralise each other's Mangal Dosha. This is one of the most asked questions in Indian matchmaking and one of the most commonly misunderstood, so an API that returns clear, structured Mangal status saves platforms a lot of customer-support load.
Nadi and Bhakoot compatibility. Two specific Kootas inside the Ashtakoot system that families often ask about by name, especially Nadi (carrying weight of 8 out of 36 points) which is considered the most important single factor. Surfacing these as their own data points lets the matrimony product highlight strengths and call out concerns honestly rather than reducing everything to a single number.

Where DivineAPI sits in this picture

DivineAPI ships 8 dedicated Match Making endpoints under the Indian API category, designed to cover the full matrimony workflow:

  • Ashtakoot Milan (the 36-point Guna Milan)
  • Dashakoot Milan (the 10-Koot variant)
  • Matching Manglik Dosha (per-partner and combined Mangal status)
  • Matching Horoscope Chart (D1 chart for both partners)
  • Matching Planetary Positions
  • Matching Vimshottari Dasha (running planetary periods for both, useful for timing recommendations)
  • Matching Basic Astro (consolidated profile data)
  • Nav Pancham Yoga (a specific compatibility yoga check)

All 8 are part of the broader stack of 225 endpoints across 8 spiritual domains under one API key, which matters for matrimony platforms that also want to ship daily horoscopes, panchang-based muhurat suggestions for engagement and wedding dates, or PDF kundali reports without managing multiple integrations.

The matching endpoints support 8 Indian languages

English, Hindi, Bengali, Marathi, Tamil, Telugu, Malayalam, and Kannada. For platforms targeting users across the country, this matters more than people initially think. A Kundali report in Kannada or Bengali lands very differently than the same report in English for the family member who actually signs off on the match.

Underneath, it runs on Swiss Ephemeris, the same astronomical calculation engine based on NASA JPL ephemeris data that almost every serious astrology software is built on. The math is precise to sub-milliarcsecond accuracy, which is overkill for kundali matching but matters for any platform that wants to defend the accuracy of its compatibility scores against the family astrologer's own calculations.

The business case for matrimony product teams

Three concrete shifts unlock when kundali matching becomes a sub-second API call instead of a 45-minute consultation:

Speed of conversion

The friction between profile match and compatibility verdict collapses. Users see scores during browsing, not after a multi-day wait. This compresses the funnel from interest to family conversation, which is where most matrimony platforms actually convert to revenue.

Reach
Platforms can now confidently include kundali matching as a baseline feature for every user, including those who would not have paid for an astrologer consultation upfront. The marginal cost of a match check is the API call, fractions of a cent at scale.

Premium feature potential
With the baseline match free, platforms can stack premium offerings on top: detailed Mangal Dosha reports, Vimshottari Dasha timing recommendations for engagement and wedding dates, multilingual PDF kundali downloads, full-chart synastry, astrologer-reviewed interpretations of edge cases. Each becomes an upsell path that wasn't viable when every match required a human astrologer's time.

The platforms that move fastest here will be the ones that treat kundali matching not as a "ritual feature" to check a box, but as a serious data product worth investing in, with multilingual support, accurate dosha analysis, and the ability to surface compatibility signals beyond the single 36-point score.

Closing thought

Indian matrimony is one of the largest, oldest, and most underserved categories in consumer tech. The cultural complexity that makes it hard to build for (regional variation in matching systems, multilingual expectations, family-driven decision-making) is the same complexity that makes it defensible once you build for it well. Kundali matching APIs are now mature enough that a small product team can ship the full Ashtakoot-Dashakoot-Mangal-Nadi stack in a sprint and spend the rest of their roadmap on the experience layer that actually differentiates their platform.

If you are building or scaling a matrimony product, the Vedic astrology API category is worth a serious evaluation cycle. DivineAPI's matching stack is at divineapi.com/indian-astrology/kundali-matching-api, with a 14-day free trial.

Top comments (0)