Build an AstroTalk Alternative: Complete Vedic Astrology API Guide

An app like AstroTalk is not mainly a calculation engine. It is a marketplace that connects users with astrologers over chat, call and video, paid from a wallet, and kept busy between consultations by free daily features: a kundli, the daily panchang, a horoscope, and matchmaking. Those free features are what bring users back every morning, and every one of them depends on correct Vedic calculations: Lahiri ayanamsa, nakshatra and pada, Vimshottari dasha sequencing, Gun Milan koota scoring, panchang timing, and KP sub-lord tables. The Vedic Astrology API from RoxyAPI gives you each of these as a REST endpoint, or as Remote MCP tools if you are building an AI agent, so your team spends its engineering on the marketplace, the experience and distribution. This guide maps the architecture, then builds the core calculation features with real API calls.

What does an AstroTalk-style app need, and which part is the API?

An AstroTalk-style app needs three layers: a user app, an astrologer app, and backend services, and only one backend service is astrology calculation. That service is the one an API replaces. Everything else, the marketplace, payments and the consultation tools, is where your product differentiates.

• User app: birth details and saved kundlis, daily panchang and horoscope, a matchmaking tool, astrologer discovery and booking, chat, voice and video, and a wallet.
• Astrologer app: profile and availability, a consultation queue, a client kundli viewer, and an earnings dashboard.
• Backend services: accounts, astrologer onboarding, consultation sessions, payments, notifications, and the astrology calculation API.

The calculation layer powers every free feature that keeps users opening the app: the kundli on the profile, the morning panchang notification, the Gun Milan score before a marriage conversation, and the dasha timeline an astrologer reads during a consultation. Cache it sensibly and it stays a small line in your costs: a kundli never changes for a given birth, so cache it per user, and the daily panchang is the same for everyone in a city, so cache it per city per day.

Ready to build this? RoxyAPI Vedic Astrology API gives you kundli generation, compatibility scoring, dasha predictions and panchang on a single API key. See pricing.

How to generate a kundli using the Vedic Astrology API

A kundli is the foundation of every Vedic astrology feature. It is a birth chart showing the position of all nine grahas plus the Lagna (ascendant) across 12 houses, calculated with Lahiri ayanamsa by default and verified against NASA JPL Horizons.

Every coordinate-based chart starts with the birthplace. Resolve it once with location search, which returns latitude, longitude and an IANA timezone, so historical offsets are applied for the birth date instead of guessed:

curl "https://roxyapi.com/api/v2/location/search?q=New%20Delhi&limit=1" \
  --header "X-API-Key: YOUR_API_KEY"

The first result returns latitude 28.6214, longitude 77.2148 and timezone "Asia/Kolkata". Pass those into the birth chart:

curl -X POST https://roxyapi.com/api/v2/vedic-astrology/birth-chart \
  --header "X-API-Key: YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "date": "1990-08-15",
    "time": "10:30:00",
    "latitude": 28.6214,
    "longitude": 77.2148,
    "timezone": "Asia/Kolkata"
  }'

The response returns the 12 rashis with their grahas, the Lagna, nakshatra and pada for every planet, combustion status, yogas and interpretations. For this birth the Lagna is Virgo, in Chitra nakshatra, pada 2. You get everything you need to render a kundli wheel or a tabular chart with a single call, and the Kundli API page shows the full field list.

How to build a complete free kundli report with three API calls

Kundli apps commonly offer a free report covering the birth chart, the current dasha period and manglik status. You can replicate it with three calls on the same birth payload and the same key.

Call 1: Generate the birth chart with the request above. It gives you the full kundli: houses, grahas, Lagna, nakshatra and pada for every planet.

Call 2: Get the current dasha period

curl -X POST https://roxyapi.com/api/v2/vedic-astrology/dasha/current \
  --header "X-API-Key: YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"date":"1990-08-15","time":"10:30:00","latitude":28.6214,"longitude":77.2148,"timezone":"Asia/Kolkata"}'

This returns the active Mahadasha, Antardasha, Pratyantardasha, Sookshma and Prana dasha with the time remaining in each. For this birth the running period is Jupiter Mahadasha, Ketu Antardasha.

Call 3: Check manglik status

curl -X POST https://roxyapi.com/api/v2/vedic-astrology/dosha/manglik \
  --header "X-API-Key: YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"date":"1990-08-15","time":"10:30:00","latitude":28.6214,"longitude":77.2148,"timezone":"Asia/Kolkata"}'

The response includes present, severity, exceptions, effects and remedies. Three calls, one key, and the free kundli report is complete.

How to build a kundli matching feature with Gun Milan scoring

Kundli matching is the most requested feature in Indian matrimonial and astrology apps. The Ashtakoot Gun Milan system scores compatibility across eight kootas with a maximum of 36 points, and 18 is the common threshold for a compatible match.

The /compatibility endpoint handles the full calculation. Pass birth data for both people, each resolved through location search:

curl -X POST https://roxyapi.com/api/v2/vedic-astrology/compatibility \
  --header "X-API-Key: YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "person1": {
      "date": "1990-08-15",
      "time": "10:30:00",
      "latitude": 28.6214,
      "longitude": 77.2148,
      "timezone": "Asia/Kolkata"
    },
    "person2": {
      "date": "1992-03-22",
      "time": "07:15:00",
      "latitude": 19.0728,
      "longitude": 72.8826,
      "timezone": "Asia/Kolkata"
    }
  }'

The response returns a total out of maxScore 36, a percentage, an isCompatible boolean, a recommendation, doshas and doshaCancellations, and a breakdown of all eight kootas: Varna, Vashya, Tara, Yoni, Graha Maitri, Gana, Bhakoot and Nadi. For this pair the total is 11.5 of 36. The koota breakdown is what separates a real matchmaking feature from a single score: your users see where compatibility is strong and where caution is advised.

South Indian matchmaking uses a different system. POST /vedic-astrology/compatibility/dashakoot scores the ten poruthams with Rajju and Vedha as vetoes, and POST /vedic-astrology/compatibility/papasamyam compares malefic affliction across both charts. A pair can score well on Ashtakoot and still fail Rajju, which is why porutham and Gun Milan answer different questions. The kundli matching API page has the full schema.

How to add dosha detection to your astrology app

Dosha detection is a high-engagement feature. Users actively look up their manglik, Kaal Sarp and Sade Sati status, and each has its own endpoint with the same request format as the birth chart:

• POST /vedic-astrology/dosha/manglik checks Mars placement in houses 1, 2, 4, 7, 8 or 12 from the Lagna, with cancellation exceptions
• POST /vedic-astrology/dosha/kalsarpa checks whether all grahas fall between Rahu and Ketu
• POST /vedic-astrology/dosha/sadhesati checks whether Saturn is transiting the Moon sign or the signs beside it

Each response includes present, a severity, readable effects and a remedies array, so you can display dosha cards without any Vedic astrology knowledge on your side. Sade Sati status changes as Saturn moves, so calling /dosha/sadhesati with the current date gives users a live status, and a future date shows the next transition.

How to integrate Vimshottari dasha predictions

The Vimshottari dasha system divides a 120-year cycle across nine planetary periods, and it is the primary timing tool in Vedic astrology. Users want to know which planet governs their current period and what it means for career, relationships and health.

/dasha/current returns the running period at every level. For the complete lifetime view, use /dasha/major:

curl -X POST https://roxyapi.com/api/v2/vedic-astrology/dasha/major \
  --header "X-API-Key: YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"date":"1990-08-15","time":"10:30:00","latitude":28.6214,"longitude":77.2148,"timezone":"Asia/Kolkata"}'

This returns all nine Mahadashas with start and end dates and the dasha balance at birth, and the /dasha/sub/... endpoints drill into any period down to Sookshma. Combine the lifetime timeline with the current period to show users both where they are and the road ahead. The Vimshottari Dasha API page covers every level.

How to build a panchang feature for your app

Panchang is the Hindu almanac used for auspicious timing. Users check it daily for Tithi, Nakshatra, Yoga, Karana, Vara, sunrise and sunset, and muhurta windows, and a morning panchang notification is one of the strongest daily-return features an Indian astrology app can ship.

The /panchang/detailed endpoint returns the full daily panchang for any location and date:

curl -X POST https://roxyapi.com/api/v2/vedic-astrology/panchang/detailed \
  --header "X-API-Key: YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "date": "2026-10-04",
    "time": "06:00:00",
    "latitude": 28.6214,
    "longitude": 77.2148,
    "timezone": "Asia/Kolkata"
  }'

The response includes Tithi, Nakshatra, Yoga, Karana, Vara, sunrise, sunset, moonrise, moonset, Rahu Kaal, Yamaganda, Gulika, Abhijit and Brahma muhurta, Amrit Kalam and Varjyam, all calculated for the latitude and longitude you pass. Choghadiya and hora have their own endpoints, POST /vedic-astrology/panchang/choghadiya and POST /vedic-astrology/panchang/hora, for wedding planners, business launch tools and travel apps that need the eight day and night divisions.

How the KP astrology endpoints work for advanced apps

KP astrology (Krishnamurti Paddhati) extends classical Vedic astrology with sub-lord theory and Placidus house cusps, and professional astrologers use it for event timing. Most consumer apps offer KP only through a human astrologer, which makes it a clear differentiator for an app that exposes it directly.

The /kp/chart endpoint returns Placidus cusps, planets with star lord and sub-lord, nodes, the ascendant and significators:

curl -X POST https://roxyapi.com/api/v2/vedic-astrology/kp/chart \
  --header "X-API-Key: YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"date":"1990-08-15","time":"10:30:00","latitude":28.6214,"longitude":77.2148,"timezone":"Asia/Kolkata"}'

Separate endpoints cover KP cusps, planets, ayanamsa, horary and daily finance. The API also exposes GET endpoints for all 27 nakshatras and all 12 rashis with deity, symbol, gemstone and traits. See the full list in the Vedic Astrology API reference, which runs every endpoint live in the browser with no signup.

How do you go beyond what a Vedic-only app offers?

You go beyond it with breadth on the same key and an AI layer you control. A Vedic-only app stops at Jyotish; with RoxyAPI the same key also returns tarot spreads, numerology, Western astrology, dream symbols and more, so a new feature is a new call, not a new vendor:

curl -X POST https://roxyapi.com/api/v2/tarot/spreads/three-card \
  --header "X-API-Key: YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{}'

The second lever is an AI first reading. Connect your own model to the Vedic Remote MCP server at https://roxyapi.com/mcp/vedic-astrology, and the assistant can read a user kundli and running dasha before a human astrologer joins, grounded in calculated values rather than guesses. Your system prompt, your model, your voice. The MCP guide covers the setup, and the open source AI astrology chatbot template is a working starting point.

Accuracy is the third lever. Indian astrology users take it seriously, and a wrong nakshatra or dasha loses trust permanently. RoxyAPI publishes its proof: a median deviation of 0.05 arcseconds (0.00001 degrees) from NASA JPL Horizons in an open benchmark, and the verification matrix on the methodology page.

Frequently Asked Questions

Q: How do I generate a kundli with an API? A: Resolve the birthplace with GET /location/search, then send a POST to /vedic-astrology/birth-chart with the birth date, time, latitude, longitude and timezone. RoxyAPI returns all 12 houses, 9 grahas, the Lagna, nakshatra and pada for every planet, combustion status, yogas and interpretations in one JSON response.

Q: What is the best Vedic astrology API for an AstroTalk-style app? A: RoxyAPI covers kundli, Ashtakoot Gun Milan, South Indian porutham, Vimshottari dasha to five levels, panchang, choghadiya, doshas, KP and divisional charts, and the same key adds tarot, numerology and Western astrology. Every calculation is verified against NASA JPL Horizons, and each domain ships a Remote MCP server for AI features.

Q: How do I build a kundli app without knowing Vedic astrology? A: Use an API that handles every calculation and returns structured JSON with interpretations. You do not need to understand nakshatra boundaries or ayanamsa corrections: RoxyAPI returns the calculated values and their meaning, so you focus on the interface and the experience.

Q: Is there a kundli matching API for matrimonial apps? A: Yes. RoxyAPI POST /vedic-astrology/compatibility returns the Ashtakoot total out of 36, a percentage, a recommendation, dosha cancellations and all eight kootas, and POST /vedic-astrology/compatibility/dashakoot scores the South Indian ten porutham system with Rajju and Vedha.

Q: How accurate is a Vedic astrology API compared to desktop software? A: Accuracy depends on the ephemeris and the ayanamsa. RoxyAPI runs Roxy Ephemeris, which reads the NASA JPL DE440 ephemeris directly and is verified against NASA JPL Horizons, with Lahiri ayanamsa by default, other ayanamsa options per request, and Placidus cusps for KP.

Q: What part of an AstroTalk-style app does the API not cover? A: The marketplace: astrologer onboarding, chat, voice and video sessions, the wallet and payments, and notifications. RoxyAPI covers the calculation and interpretation layer behind every free feature, so your team builds the part that differentiates the product.

Build your Vedic astrology app today

Every calculation an AstroTalk-style app depends on is available as a REST endpoint: kundli, Gun Milan and porutham, Vimshottari dasha timelines, dosha detection, daily panchang, divisional charts and KP, all on the same key and the same request format, with tarot, numerology and Western astrology beside them. Start with the RoxyAPI Vedic Astrology API and compare plans and pricing.