Kundli API

Kundli Calculator API

POST/vedic-astrology/birth-chart

Calculate complete Vedic birth chart (Janam Kundli, natal chart) with all 9 planetary positions (Sun through Ketu) plus Ascendant (Lagna). Kundli calculator API for astrology apps, matrimonial sites. Returns accurate graha positions grouped by zodiac signs (rashis) with nakshatra details and pada. Perfect for kundli generation, horoscope matching, and Vedic astrology software integration.

Location first, chart second

The Kundli API needs latitude, longitude, and timezone. Never ask users to type coordinates. Resolve a city with the Location endpoint first, then feed the result into the request. Timezone accepts a decimal offset or an IANA name.

1 Resolve the location

GET
curl "https://roxyapi.com/api/v2/location/search?q=New York" \
  -H "X-API-Key: YOUR_KEY"
# -> cities[0]: { latitude, longitude, timezone: "America/New_York" }

2 Call the Kundli endpoint

POST /vedic-astrology/birth-chart
# feed latitude, longitude and timezone from step 1
POST https://roxyapi.com/api/v2/vedic-astrology/birth-chart

Request

POST /api/v2/vedic-astrology/birth-chart

Parameters

ParameterTypeDescription
langquerystring enumResponse language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. Default en.

Request body

FieldTypeDescription
date*string (date)Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).
time*string (time)Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.
latitude*numberBirth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.
longitude*numberBirth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.
timezonenumber or stringTimezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.

Example request

POST /vedic-astrology/birth-chart
{
  "date": "1990-07-04",
  "time": "10:12:00",
  "latitude": 28.6139,
  "longitude": 77.209
}

Response

Structured JSON with documented fields, verified against NASA JPL Horizons across 828 gold-standard tests. Not hallucinated text.

200 OK
{
  "aries": {
    "rashi": "aries",
    "signs": []
  },
  "meta": {
    "Sun": {
      "graha": "Sun",
      "rashi": "Leo",
      "longitude": 132.45,
      "nakshatra": {
        "name": "Magha",
        "pada": 2,
        "key": 9,
        "lord": "Ketu"
      },
      "isRetrograde": false,
      "house": 5,
      "awastha": "Vriddha"
    },
    "Moon": {
      "graha": "Moon",
      "rashi": "Cancer",
      "longitude": 98.32,
      "nakshatra": {
        "name": "Punarvasu",
        "pada": 4,
        "key": 6,
        "lord": "Jupiter"
      },
      "isRetrograde": false,
      "house": 4,
      "awastha": "Yuva"
    }
  }
}

Response fields

FieldTypeDescription
aries*object
aries.rashi*stringZodiac sign name in lowercase.
aries.signs*array of objectPlanets placed in this zodiac sign.
aries.signs[].graha*stringPlanet (graha) placed in this sign.
aries.signs[].longitude*numberSidereal longitude in degrees (0-360) using Lahiri ayanamsa.
aries.signs[].nakshatra*object
aries.signs[].nakshatra.name*stringNakshatra (lunar mansion, 1 of 27) the planet occupies.
aries.signs[].nakshatra.pada*numberNakshatra pada (quarter, 1-4). Each nakshatra has 4 padas of 3 degrees 20 each.
aries.signs[].nakshatra.key*numberNakshatra index (1-27) in the zodiac sequence starting from Ashwini.
aries.signs[].nakshatra.lord*string enumVimshottari ruling planet of this nakshatra. One of the nine grahas (Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury). Drives the dasha sequence and the nakshatra qualities.
aries.signs[].isRetrograde*booleanTrue if planet is in retrograde motion (appears to move backward). Retrograde planets have altered significations.
aries.signs[].houseintegerBhava (house) number 1-12, counted whole-sign from the Lagna (house 1 is the Lagna rashi). Present on the D1 birth chart; divisional charts (navamsa, varga) omit it.
aries.signs[].awasthastring enumBaladi avastha, the planetary age-state set by the graha degree within its sign: Bala (infant), Kumara (child), Yuva (adult, strongest results), Vriddha (old), Mrita (dead, weakest). Bands run forward in odd signs and reversed in even signs. D1 birth chart only.
taurus*object
Show all fields
FieldTypeDescription
taurus.rashi*stringZodiac sign name in lowercase.
taurus.signs*array of objectPlanets placed in this zodiac sign.
taurus.signs[].graha*stringPlanet (graha) placed in this sign.
taurus.signs[].longitude*numberSidereal longitude in degrees (0-360) using Lahiri ayanamsa.
taurus.signs[].nakshatra*object
taurus.signs[].nakshatra.name*stringNakshatra (lunar mansion, 1 of 27) the planet occupies.
taurus.signs[].nakshatra.pada*numberNakshatra pada (quarter, 1-4). Each nakshatra has 4 padas of 3 degrees 20 each.
taurus.signs[].nakshatra.key*numberNakshatra index (1-27) in the zodiac sequence starting from Ashwini.
taurus.signs[].nakshatra.lord*string enumVimshottari ruling planet of this nakshatra. One of the nine grahas (Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury). Drives the dasha sequence and the nakshatra qualities.
taurus.signs[].isRetrograde*booleanTrue if planet is in retrograde motion (appears to move backward). Retrograde planets have altered significations.
taurus.signs[].houseintegerBhava (house) number 1-12, counted whole-sign from the Lagna (house 1 is the Lagna rashi). Present on the D1 birth chart; divisional charts (navamsa, varga) omit it.
taurus.signs[].awasthastring enumBaladi avastha, the planetary age-state set by the graha degree within its sign: Bala (infant), Kumara (child), Yuva (adult, strongest results), Vriddha (old), Mrita (dead, weakest). Bands run forward in odd signs and reversed in even signs. D1 birth chart only.
gemini*object
gemini.rashi*stringZodiac sign name in lowercase.
gemini.signs*array of objectPlanets placed in this zodiac sign.
gemini.signs[].graha*stringPlanet (graha) placed in this sign.
gemini.signs[].longitude*numberSidereal longitude in degrees (0-360) using Lahiri ayanamsa.
gemini.signs[].nakshatra*object
gemini.signs[].nakshatra.name*stringNakshatra (lunar mansion, 1 of 27) the planet occupies.
gemini.signs[].nakshatra.pada*numberNakshatra pada (quarter, 1-4). Each nakshatra has 4 padas of 3 degrees 20 each.
gemini.signs[].nakshatra.key*numberNakshatra index (1-27) in the zodiac sequence starting from Ashwini.
gemini.signs[].nakshatra.lord*string enumVimshottari ruling planet of this nakshatra. One of the nine grahas (Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury). Drives the dasha sequence and the nakshatra qualities.
gemini.signs[].isRetrograde*booleanTrue if planet is in retrograde motion (appears to move backward). Retrograde planets have altered significations.
gemini.signs[].houseintegerBhava (house) number 1-12, counted whole-sign from the Lagna (house 1 is the Lagna rashi). Present on the D1 birth chart; divisional charts (navamsa, varga) omit it.
gemini.signs[].awasthastring enumBaladi avastha, the planetary age-state set by the graha degree within its sign: Bala (infant), Kumara (child), Yuva (adult, strongest results), Vriddha (old), Mrita (dead, weakest). Bands run forward in odd signs and reversed in even signs. D1 birth chart only.
cancer*object
cancer.rashi*stringZodiac sign name in lowercase.
cancer.signs*array of objectPlanets placed in this zodiac sign.
cancer.signs[].graha*stringPlanet (graha) placed in this sign.
cancer.signs[].longitude*numberSidereal longitude in degrees (0-360) using Lahiri ayanamsa.
cancer.signs[].nakshatra*object
cancer.signs[].nakshatra.name*stringNakshatra (lunar mansion, 1 of 27) the planet occupies.
cancer.signs[].nakshatra.pada*numberNakshatra pada (quarter, 1-4). Each nakshatra has 4 padas of 3 degrees 20 each.
cancer.signs[].nakshatra.key*numberNakshatra index (1-27) in the zodiac sequence starting from Ashwini.
cancer.signs[].nakshatra.lord*string enumVimshottari ruling planet of this nakshatra. One of the nine grahas (Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury). Drives the dasha sequence and the nakshatra qualities.
cancer.signs[].isRetrograde*booleanTrue if planet is in retrograde motion (appears to move backward). Retrograde planets have altered significations.
cancer.signs[].houseintegerBhava (house) number 1-12, counted whole-sign from the Lagna (house 1 is the Lagna rashi). Present on the D1 birth chart; divisional charts (navamsa, varga) omit it.
cancer.signs[].awasthastring enumBaladi avastha, the planetary age-state set by the graha degree within its sign: Bala (infant), Kumara (child), Yuva (adult, strongest results), Vriddha (old), Mrita (dead, weakest). Bands run forward in odd signs and reversed in even signs. D1 birth chart only.
leo*object
leo.rashi*stringZodiac sign name in lowercase.
leo.signs*array of objectPlanets placed in this zodiac sign.
leo.signs[].graha*stringPlanet (graha) placed in this sign.
leo.signs[].longitude*numberSidereal longitude in degrees (0-360) using Lahiri ayanamsa.
leo.signs[].nakshatra*object
leo.signs[].nakshatra.name*stringNakshatra (lunar mansion, 1 of 27) the planet occupies.
leo.signs[].nakshatra.pada*numberNakshatra pada (quarter, 1-4). Each nakshatra has 4 padas of 3 degrees 20 each.
leo.signs[].nakshatra.key*numberNakshatra index (1-27) in the zodiac sequence starting from Ashwini.
leo.signs[].nakshatra.lord*string enumVimshottari ruling planet of this nakshatra. One of the nine grahas (Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury). Drives the dasha sequence and the nakshatra qualities.
leo.signs[].isRetrograde*booleanTrue if planet is in retrograde motion (appears to move backward). Retrograde planets have altered significations.
leo.signs[].houseintegerBhava (house) number 1-12, counted whole-sign from the Lagna (house 1 is the Lagna rashi). Present on the D1 birth chart; divisional charts (navamsa, varga) omit it.
leo.signs[].awasthastring enumBaladi avastha, the planetary age-state set by the graha degree within its sign: Bala (infant), Kumara (child), Yuva (adult, strongest results), Vriddha (old), Mrita (dead, weakest). Bands run forward in odd signs and reversed in even signs. D1 birth chart only.
virgo*object
virgo.rashi*stringZodiac sign name in lowercase.
virgo.signs*array of objectPlanets placed in this zodiac sign.
virgo.signs[].graha*stringPlanet (graha) placed in this sign.
virgo.signs[].longitude*numberSidereal longitude in degrees (0-360) using Lahiri ayanamsa.
virgo.signs[].nakshatra*object
virgo.signs[].nakshatra.name*stringNakshatra (lunar mansion, 1 of 27) the planet occupies.
virgo.signs[].nakshatra.pada*numberNakshatra pada (quarter, 1-4). Each nakshatra has 4 padas of 3 degrees 20 each.
virgo.signs[].nakshatra.key*numberNakshatra index (1-27) in the zodiac sequence starting from Ashwini.
virgo.signs[].nakshatra.lord*string enumVimshottari ruling planet of this nakshatra. One of the nine grahas (Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury). Drives the dasha sequence and the nakshatra qualities.
virgo.signs[].isRetrograde*booleanTrue if planet is in retrograde motion (appears to move backward). Retrograde planets have altered significations.
virgo.signs[].houseintegerBhava (house) number 1-12, counted whole-sign from the Lagna (house 1 is the Lagna rashi). Present on the D1 birth chart; divisional charts (navamsa, varga) omit it.
virgo.signs[].awasthastring enumBaladi avastha, the planetary age-state set by the graha degree within its sign: Bala (infant), Kumara (child), Yuva (adult, strongest results), Vriddha (old), Mrita (dead, weakest). Bands run forward in odd signs and reversed in even signs. D1 birth chart only.
libra*object
libra.rashi*stringZodiac sign name in lowercase.

Supported options

lang

entrdeeshiptfrru

Call it in your language in seconds.

Every snippet is generated from the live OpenAPI spec, so method names, parameters, and fields always match production.

TypeScript
import { createRoxy } from '@roxyapi/sdk'

const roxy = createRoxy(process.env.ROXY_API_KEY!)
const { data } = await roxy.vedicAstrology.generateBirthChart({ body: { date: '1990-07-04', time: '10:12:00', latitude: 28.6139, longitude: 77.209 } })
Install: npm install @roxyapi/sdk

Prefer to try before you write code? Run this Vedic Astrology endpoint live in the API playground and inspect a real production response.

Remote MCP for AI agents

Every Vedic Astrology endpoint is a callable tool on the Remote MCP server over Streamable HTTP. No local setup, no Docker. Claude, ChatGPT, Cursor, and any MCP client auto-discover the tools and ground their answers in verified data.

Claude Code / Cursor
claude mcp add --transport http \
  roxy-vedic-astrology https://roxyapi.com/mcp/vedic-astrology \
  --header "X-API-Key: YOUR_KEY"

Tool name for POST /vedic-astrology/birth-chart: post_vedic_astrology_birth_chart. Full MCP setup guide

What you can build

Matrimonial matchmaking platforms - automate Gun Milan compatibility scoring, Manglik dosha checks, Navamsa spouse analysis, and generate match reports with remedies for Shaadi.com-style features

Daily horoscope and prediction apps - fetch planetary transits, current Dasha periods, Panchang data, and birth star forecasts to power personalized daily readings at consumer-app scale

Kundli generation and PDF report services - combine D1/D9 charts, planetary positions, Dasha timelines, yoga detection, and dosha analysis into automated birth chart reports

KP horary and event prediction apps - build stellar astrology software with significator analysis, cusp sub-lords, and 249-level precision for answering when/yes-no questions

Spiritual wellness and calendar apps - integrate Panchang for Hindu festival dates, fasting calendars, temple muhurat selection, and Nakshatra-based meditation schedules

AI astrology chatbots and virtual consultants - power conversational AI with structured Vedic calculations, compatibility queries, Dasha predictions, and remedy suggestions via ChatGPT plugins or MCP integration

Drop-in UI components

Render Kundli API responses without building charts yourself. These open source, framework-agnostic web components take the typed response and draw it, in React, Vue, Svelte, Angular, plain HTML, and WordPress.

<roxy-vedic-kundli><roxy-vedic-planets-table>
See them live on Roxy UI

Related capabilities

Kundli API FAQ

What does the Kundli API return?

Calculate complete Vedic birth chart (Janam Kundli, natal chart) with all 9 planetary positions (Sun through Ketu) plus Ascendant (Lagna). Every response is structured JSON with documented fields, not free text, so you map it straight into your product.

How do I authenticate with the Kundli API?

Pass your key in the X-API-Key header on every request. Keys are delivered instantly at checkout with no approval queue. Use a secret sk key server side, or mint a publishable pk key locked to your origins for browser and no-code use.

Does the Kundli API support multiple languages?

Yes. Append the lang query parameter to any endpoint for responses in English, German, Spanish, French, Hindi, Portuguese, Russian and Turkish. The translated payload includes the full interpretation text, not just field labels.

Do I need coordinates to call the Kundli API?

No. Call GET /location/search with a city name first, then pass latitude, longitude, and timezone from the first result into the request. Never ask users to type coordinates. Timezone accepts a decimal offset or an IANA name.

Is the Kundli API available over Remote MCP for AI agents?

Yes. Every endpoint is exposed as a callable tool on the Remote MCP server at https://roxyapi.com/mcp/vedic-astrology over Streamable HTTP, so Claude, ChatGPT, Cursor, and any MCP client auto-discover it with no local setup or Docker.

How is the Kundli API billed?

Flat pricing: 1 request equals 1 quota unit, REST and MCP identical, with no credit weighting or per-token markup. Every plan includes all 12 domains, so the Kundli API is included at no extra cost.

What lang values does the Kundli API accept?

The lang parameter accepts en, tr, de, es, hi, pt, fr, ru. Case-insensitive where it is a path value.

Start using Kundli API today.

Launch your Jyotish or KP astrology product in days. Not months.

All 12 domains included with every plan. Every endpoint, MCP server, SDK, and starters.

Plans from $39/mo, starting at $2.70 per domain on annual billing. No credit card required for testing.

View Pricing & Get API Key