Navamsa Chart API
Marriage Compatibility Calculator
Included with every plan (at no extra cost)
Calculate Navamsa (D9 divisional chart) for marriage compatibility analysis, spouse prediction, and spiritual life assessment. Navamsa calculator API reveals planetary strength in married life. Each planetary position is divided into 9 parts for accurate marriage astrology. Detects Vargottama planets (exalted status). Essential for matrimonial matching, relationship prediction, and marital harmony analysis in Vedic astrology.
Location first, chart second
The Navamsa Chart 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
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 Navamsa Chart endpoint
# feed latitude, longitude and timezone from step 1
POST https://roxyapi.com/api/v2/vedic-astrology/navamsaRequest
POST /api/v2/vedic-astrology/navamsa
Parameters
| Parameter | Type | Description |
|---|---|---|
| langquery | string enum | Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English. Default en. |
Request body
| Field | Type | Description |
|---|---|---|
| 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* | number | Birth 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* | number | Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240. |
| timezone | number or string | Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5. |
| ayanamsa | string enum | Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. "kp-newcomb" and "kp-old" are the two Krishnamurti Paddhati frames. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it. |
| ayanamsaValue | number | Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source. |
Example request
{
"date": "1990-07-04",
"time": "10:12:00",
"latitude": 28.6139,
"longitude": 77.209,
"timezone": 5.5,
"ayanamsa": "lahiri",
"ayanamsaValue": 24
}Response
Structured JSON with documented fields, covered by 13,405 automated tests per deploy, 3,620 of them gold-standard tests verified against NASA JPL Horizons. Not hallucinated text.
{
"frame": {
"ayanamsa": "lahiri",
"ayanamsaDegrees": 23.728208791839048
},
"chart": {
"frame": {
"ayanamsa": "lahiri",
"ayanamsaDegrees": 23.728208791839048
},
"aries": {
"rashi": "aries",
"signs": [
{
"graha": "Mars",
"nakshatra": {
"anga": "nakshatra",
"key": 1,
"ratio": 0.03861131691362409,
"abhijit": false,
"left": 12.818515774485013,
"name": "Ashwini",
"pada": 1,
"lord": "Ketu"
},
"longitude": 0.5148175588483213,
"isRetrograde": false,
"house": 8
},
{
"graha": "Mercury",
"nakshatra": {
"anga": "nakshatra",
"key": 7,
"ratio": 0.002438114262190627,
"abhijit": false,
"left": 13.300825143170792,
"name": "Punarvasu",
"pada": 1,
"lord": "Jupiter"
},
"longitude": 80.03250819016255,
"isRetrograde": false,
"house": 8
}
]
},
"taurus": {
"rashi": "taurus",
"signs": [
{
"graha": "Jupiter",
"nakshatra": {
"anga": "nakshatra",
"key": 7,
"ratio": 0.471566817146049,
"abhijit": false,
"left": 7.045775771386014,
"name": "Punarvasu",
"pada": 2,
"lord": "Jupiter"
},
"longitude": 86.28755756194732,
"isRetrograde": false,
"house": 9
},
{
"graha": "Rahu",
"nakshatra": {
"anga": "nakshatra",
"key": 22,
"ratio": 0.3734890910423166,
"abhijit": false,
"left": 8.353478786102446,
"name": "Shravana",
"pada": 2,
"lord": "Moon"
},
"longitude": 284.9798545472309,
"isRetrograde": true,
"house": 9
}
]
},
"gemini": {
"rashi": "gemini",
"signs": [
{
"graha": "Venus",
"nakshatra": {
"anga": "nakshatra",
"key": 4,
"ratio": 0.5382611176220545,
"abhijit": false,
"left": 6.1565184317059405,
"name": "Rohini",
"pada": 3,
"lord": "Moon"
},
"longitude": 47.176814901627395,
"isRetrograde": false,
"house": 10
}
]
},
"cancer": {
"rashi": "cancer",
"signs": []
},
"leo": {
"rashi": "leo",
"signs": [
{
"graha": "Moon",
"nakshatra": {
"anga": "nakshatra",
"key": 17,
"ratio": 0.15018455945281275,
"abhijit": false,
"left": 11.330872540629164,
"name": "Anuradha",
"pada": 1,
"lord": "Saturn"
},
"longitude": 215.3357941260375,
"isRetrograde": false,
"house": 12
}
]
},
"virgo": {
"rashi": "virgo",
"signs": [
{
"graha": "Lagna",
"nakshatra": {
"anga": "nakshatra",
"key": 11,
"ratio": 0.3784062191982829,
"abhijit": false,
"left": 8.287917077356228,
"name": "Purva Phalguni",
"pada": 2,
"lord": "Venus"
},
"longitude": 138.37874958931044,
"isRetrograde": false,
"house": 1
}
]
},
"libra": {
"rashi": "libra",
"signs": []
},
"scorpio": {
"rashi": "scorpio",
"signs": [
{
"graha": "Ketu",
"nakshatra": {
"anga": "nakshatra",
"key": 8,
"ratio": 0.8734890910423172,
"abhijit": false,
"left": 1.6868121194357713,
"name": "Pushya",
"pada": 4,
"lord": "Saturn"
},
"longitude": 104.9798545472309,
"isRetrograde": true,
"house": 3
}
]
},
"sagittarius": {
"rashi": "sagittarius",
"signs": [
{
"graha": "Saturn",
"nakshatra": {
"anga": "nakshatra",
"key": 21,
"ratio": 0.17985597205895854,
"abhijit": false,
"left": 10.935253705880553,
"name": "Uttara Ashadha",
"pada": 1,
"lord": "Sun"
},
"longitude": 269.06474629411946,
"isRetrograde": true,
"house": 4
}
]
},
"capricorn": {
"rashi": "capricorn",
"signs": []
},
"aquarius": {
"rashi": "aquarius",
"signs": []
},
"pisces": {
"rashi": "pisces",
"signs": [
{
"graha": "Sun",
"nakshatra": {
"anga": "nakshatra",
"key": 6,
"ratio": 0.8680896274786136,
"abhijit": false,
"left": 1.7588049669518178,
"name": "Ardra",
"pada": 4,
"lord": "Rahu"
},
"longitude": 78.24119503304819,
"isRetrograde": false,
"house": 7
}
]
},
"meta": {
"Sun": {
"graha": "Sun",
"rashi": "Pisces",
"longitude": 78.24119503304819,
"latitude": -0.0001328385398282796,
"nakshatra": {
"anga": "nakshatra",
"key": 6,
"ratio": 0.8680896274786136,
"abhijit": false,
"left": 1.7588049669518178,
"name": "Ardra",
"pada": 4,
"lord": "Rahu"
},
"isRetrograde": false,
"house": 7
},
"Moon": {
"graha": "Moon",
"rashi": "Leo",
"longitude": 215.3357941260375,
"latitude": -4.85528448436199,
"nakshatra": {
"anga": "nakshatra",
"key": 17,
"ratio": 0.15018455945281275,
"abhijit": false,
"left": 11.330872540629164,
"name": "Anuradha",
"pada": 1,
"lord": "Saturn"
},
"isRetrograde": false,
"house": 12
},
"Mars": {
"graha": "Mars",
"rashi": "Aries",
"longitude": 0.5148175588483213,
"latitude": -2.057998697195424,
"nakshatra": {
"anga": "nakshatra",
"key": 1,
"ratio": 0.03861131691362409,
"abhijit": false,
"left": 12.818515774485013,
"name": "Ashwini",
"pada": 1,
"lord": "Ketu"
},
"isRetrograde": false,
"house": 8
},
"Mercury": {
"graha": "Mercury",
"rashi": "Aries",
"longitude": 80.03250819016255,
"latitude": 1.460070348638619,
"nakshatra": {
"anga": "nakshatra",
"key": 7,
"ratio": 0.002438114262190627,
"abhijit": false,
"left": 13.300825143170792,
"name": "Punarvasu",
"pada": 1,
"lord": "Jupiter"
},
"isRetrograde": false,
"house": 8
},
"Jupiter": {
"graha": "Jupiter",
"rashi": "Taurus",
"longitude": 86.28755756194732,
"latitude": 0.21241046115946105,
"nakshatra": {
"anga": "nakshatra",
"key": 7,
"ratio": 0.471566817146049,
"abhijit": false,
"left": 7.045775771386014,
"name": "Punarvasu",
"pada": 2,
"lord": "Jupiter"
},
"isRetrograde": false,
"house": 9
},
"Venus": {
"graha": "Venus",
"rashi": "Gemini",
"longitude": 47.176814901627395,
"latitude": -1.4176921333049444,
"nakshatra": {
"anga": "nakshatra",
"key": 4,
"ratio": 0.5382611176220545,
"abhijit": false,
"left": 6.1565184317059405,
"name": "Rohini",
"pada": 3,
"lord": "Moon"
},
"isRetrograde": false,
"house": 10
},
"Saturn": {
"graha": "Saturn",
"rashi": "Sagittarius",
"longitude": 269.06474629411946,
"latitude": 0.09065030559754866,
"nakshatra": {
"anga": "nakshatra",
"key": 21,
"ratio": 0.17985597205895854,
"abhijit": false,
"left": 10.935253705880553,
"name": "Uttara Ashadha",
"pada": 1,
"lord": "Sun"
},
"isRetrograde": true,
"house": 4
},
"Rahu": {
"graha": "Rahu",
"rashi": "Taurus",
"longitude": 284.9798545472309,
"latitude": 0,
"nakshatra": {
"anga": "nakshatra",
"key": 22,
"ratio": 0.3734890910423166,
"abhijit": false,
"left": 8.353478786102446,
"name": "Shravana",
"pada": 2,
"lord": "Moon"
},
"isRetrograde": true,
"house": 9
},
"Ketu": {
"graha": "Ketu",
"rashi": "Scorpio",
"longitude": 104.9798545472309,
"latitude": 0,
"nakshatra": {
"anga": "nakshatra",
"key": 8,
"ratio": 0.8734890910423172,
"abhijit": false,
"left": 1.6868121194357713,
"name": "Pushya",
"pada": 4,
"lord": "Saturn"
},
"isRetrograde": true,
"house": 3
},
"Lagna": {
"graha": "Lagna",
"rashi": "Virgo",
"longitude": 138.37874958931044,
"nakshatra": {
"anga": "nakshatra",
"key": 11,
"ratio": 0.3784062191982829,
"abhijit": false,
"left": 8.287917077356228,
"name": "Purva Phalguni",
"pada": 2,
"lord": "Venus"
},
"isRetrograde": false,
"house": 1
}
}
},
"vargottama": [
"Mars",
"Saturn"
],
"vargottamaExplanation": "Vargottama planets occupy the same zodiac sign in both D1 (birth chart) and D9 (Navamsa chart), indicating exceptional strength and purity. Your Vargottama planets (Mars, Saturn) deliver their full results with minimal affliction, bringing stability and success in their significations. This is considered highly auspicious, especially for benefics like Jupiter and Venus, as it doubles positive effects in marriage, spirituality, and overall life prosperity."
}Response fields
| Field | Type | Description |
|---|---|---|
| chart* | object | Navamsa (D9) divisional chart showing planetary positions across 12 rashi houses plus a meta lookup. Same structure as the birth chart response. |
| chart.meta* | object | Planet positions in the Navamsa (D9) chart keyed by planet name. Contains all 9 Navagraha plus Lagna. |
| chart.aries* | object | One of the 12 navamsa rashi-house buckets (aries shown; taurus through pisces follow the identical shape). Each lists the planets placed in that sign. |
| chart.aries.rashi* | string | Zodiac sign name in lowercase. Always equals the key of the navamsa rashi-house block it sits in. |
| chart.aries.signs* | array of object | Planets placed in this navamsa sign. |
| chart.aries.signs[].graha* | string | Planet (graha) placed in this navamsa sign. |
| chart.aries.signs[].longitude* | number | Original sidereal longitude in degrees (0-360), same as the D1 birth chart. Preserved for cross-chart reference. |
| chart.aries.signs[].nakshatra* | object | Nakshatra (lunar mansion) data for this planet, carried over from the D1 chart. |
| chart.aries.signs[].isRetrograde* | boolean | True if the planet is in retrograde motion. |
| chart.aries.signs[].house | integer | Bhava (house) number 1-12 in the Navamsa chart, counted whole-sign from the D9 Lagna. |
| frame* | object | The sidereal frame this response was computed in, so a cached or forwarded payload is self describing. |
| frame.ayanamsa* | string | Sidereal frame this chart was cast in, echoing the ayanamsa request field. "lahiri" when the field was omitted. |
| frame.ayanamsaDegrees* | number | Degrees actually subtracted from every tropical longitude to produce this chart, read at the birth instant. Subtract it back to recover the tropical positions, or compare it against your reference software to confirm you are in the same frame before chasing a placement difference. |
| vargottama* | array of string | Planets that are Vargottama (same sign in D1 and D9) |
Show all fieldsShow fewer fields
| Field | Type | Description |
|---|---|---|
| vargottamaExplanation* | string | Explanation of Vargottama significance |
Supported options
lang
ayanamsa
Call it in your language.
Every snippet is generated from the live OpenAPI spec, so method names, parameters, and fields always match production.
import { createRoxy } from '@roxyapi/sdk'
const roxy = createRoxy(process.env.ROXY_API_KEY!)
const { data } = await roxy.vedicAstrology.generateNavamsa({ body: { date: '1990-07-04', time: '10:12:00', latitude: 28.6139, longitude: 77.209 } })Install: npm install @roxyapi/sdk
from roxy_sdk import create_roxy
roxy = create_roxy("YOUR_API_KEY")
result = roxy.vedic_astrology.generate_navamsa(date='1990-07-04', time='10:12:00', latitude=28.6139, longitude=77.209)Install: pip install roxy-sdk
use function RoxyAPI\Sdk\createRoxy;
$roxy = createRoxy(getenv('ROXY_API_KEY'));
$result = $roxy->vedicAstrology->generateNavamsa(date: '1990-07-04', time: '10:12:00', latitude: 28.6139, longitude: 77.209);Install: composer require roxyapi/sdk
using RoxyApi;
var roxy = new RoxyClient(Environment.GetEnvironmentVariable("ROXY_API_KEY")!);
var result = await roxy.VedicAstrology.Navamsa.PostAsync(new() { /* request fields above */ });Install: dotnet add package RoxyApi.Sdk
import roxyapi "github.com/RoxyAPI/sdk-go"
roxy, _ := roxyapi.NewRoxy(os.Getenv("ROXY_API_KEY"))
resp, _ := roxy.VedicAstrology.GenerateNavamsa(ctx, nil, roxyapi.GenerateNavamsaJSONRequestBody{ /* request fields above */ })Install: go get github.com/RoxyAPI/sdk-go
curl -X POST "https://roxyapi.com/api/v2/vedic-astrology/navamsa" \
-H "X-API-Key: YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"date":"1990-07-04","time":"10:12:00","latitude":28.6139,"longitude":77.209}'Prefer to try before you write code? Run this Vedic Astrology endpoint live in the API playground and inspect a real production response.
More Navamsa Chart endpoints
The Navamsa Chart API bundles these related endpoints under one key.
Get divisional chart (Varga) - D2 to D60 Calculator
Calculate any Vedic divisional chart (Varga) from D2 Hora to D60 Shashtiamsa. Divisional charts divide each zodiac sign into smaller segments to reveal detailed insights about specific life areas: wealth (D2), siblings (D3), property (D4), children (D7), marriage (D9), career (D10), parents (D12), vehicles (D16), spirituality (D20), education (D24), strength (D27), misfortunes (D30), merit (D40), character (D45), and past life karma (D60). Based on Brihat Parashara Hora Shastra (BPHS) Shodasha Varga system. Detects Vargottama planets (same sign in D1 and selected chart).
Try it liveRemote 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 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/navamsa: post_vedic_astrology_navamsa. Full MCP setup guide
What you can build
Kundli generation and PDF report services - combine D1/D9 charts, planetary positions, Dasha timelines, yoga detection, and dosha analysis into automated birth chart reports
Matrimonial matchmaking platforms - automate Gun Milan compatibility scoring, the South Indian ten porutham sheet with its Rajju and Vedha vetoes, Papasamyam malefic balance, Manglik dosha checks, Navamsa spouse analysis, and generate match reports with remedies for Shaadi.com-style features
Daily horoscope and prediction apps - one call composes the gochara verdicts, the panchang limbs with their validity windows, the running Dasha chain and the per-native tarabala and chandrabala into a single dated reading with a reproducible strength score, so a consumer-app daily screen is one request rather than five stitched together
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
Spiritual wellness and calendar apps - integrate Panchang for Hindu festival dates, fasting calendars, temple muhurat selection, and Nakshatra-based meditation schedules
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
Drop-in UI components and no-code widgets.
Render Navamsa Chart API responses without building charts yourself. Install the npm package and drop these into Next.js, React, Vue, Svelte, Angular, or plain HTML, or embed the very same component on Squarespace, Wix, or WordPress by pasting one snippet, with no backend and no build step. They belong to one library that covers the entire spiritual stack rather than astrology alone, MIT licensed and included in every plan at no extra cost, never a separate product and never an upsell. The Navamsa Chart API calculations, the interface that renders them, and the Remote MCP your agent calls, all behind one key, end to end.
Show all Navamsa Chart UI componentsShow fewer Navamsa Chart UI components
| Element | Renders |
|---|---|
| <roxy-divisional-chart> | Generic divisional varga wheel from D2 Hora to D60 Shashtiamsa |
Related capabilities
Navamsa Chart API FAQ
What does the Navamsa Chart API return?
Calculate Navamsa (D9 divisional chart) for marriage compatibility analysis, spouse prediction, and spiritual life assessment. 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 Navamsa Chart 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 Navamsa Chart 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 Navamsa Chart 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 Navamsa Chart 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 Navamsa Chart 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 18 domains, so the Navamsa Chart API is included at no extra cost.
What ayanamsa values does the Navamsa Chart API accept?
The ayanamsa parameter accepts kp-newcomb, kp-old, lahiri, raman, custom. Case-insensitive where it is a path value.
Start using Navamsa Chart API today.
Kundli, panchang and KP charts that state the ayanamsa they used and the classical rule behind each verdict.
All 18 domains included with every plan. Every endpoint, MCP server, SDK, and templates.
Plans from $39/mo, starting at $1.80 per domain on annual billing. No credit card required for testing.
View Pricing & Get API Key