Pillar A — How it works

Published 2026-05-12 · Updated 2026-06-18 · By Avinash Chandan, Founder, Navamsha

D1 vs D9 Navamsha: Why the Divisional Chart Matters and How to Fetch It

The D1 chart (Rashi or Lagna chart) maps graha positions in the twelve zodiac signs at birth, while the D9 Navamsha chart is the ninth harmonic divisional chart — each sign subdivided into nine parts — used to assess marriage, dharma, and planetary strength.

Most Kundli apps show D1 by default, but Parashari analysis treats D9 as essential — especially for Venus, the 7th lord, and the Moon. Navamsha exposes D1 via /kundali/basic and D9 via /divisional/d9 with shared Swiss Ephemeris and Lahiri ayanamsa metadata.

What D1 tells you

D1 is the primary birth chart: lagna (ascendant), planetary signs, whole-sign houses, and Nakshatra placements. It drives general life themes — career house, health house, planetary yogas.

The Navamsha Kundali API returns ascendant, all classical grahas, Nakshatra data, and raw longitudes suitable for downstream divisional or Dasha modules.

What D9 adds

D9 divides each 30° sign into nine 3°20′ Navamshas, assigning each planet a refined sign placement. Classical texts use D9 for marriage quality, spouse nature, spiritual inclination, and whether a planet's promise in D1 is supported.

• Vargottama: planet in same sign in D1 and D9 — considered strengthened.
• 7th house and Venus in D9: marriage and relationship tone.
• Atmakaraka in D9: deeper soul-level themes in Jaimini analysis.
• Planet in own sign or exaltation in D9: supports D1 indications.

How Navamsha division is calculated

Given a planet's sidereal longitude, the engine determines its D1 sign and degree within sign, then maps that degree into one of nine Navamsha segments using deterministic Shodashvarga rules.

The same Lahiri sidereal longitudes feed D1 and D9, so charts stay internally consistent. Metadata stamps formula version divisional.shodashvarga.v1 for validation.

API pattern: fetch D1 and D9 together

Production apps typically call basic Kundali for the main chart UI, then D9 for a detail tab or compatibility prep. Both use the same birth payload — no duplicate ephemeris logic on your side.

curl -X POST "https://api.navamsha.in/api/v1/kundali/basic" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "year": 1995, "month": 8, "date": 15, "hours": 14, "minutes": 30, "seconds": 0, "latitude": 19.0760, "longitude": 72.8777, "timezone": 5.5, "settings": { "observation_point": "topocentric", "ayanamsha": "lahiri", "language": "en" } }'

import httpx

birth = {
    "year": 1995, "month": 8, "date": 15,
    "hours": 14, "minutes": 30, "seconds": 0,
    "latitude": 19.0760, "longitude": 72.8777, "timezone": 5.5,
    "settings": {"ayanamsha": "lahiri", "observation_point": "topocentric"},
}
headers = {"X-API-Key": "YOUR_API_KEY"}

d1 = httpx.post("https://api.navamsha.in/api/v1/kundali/basic", headers=headers, json=birth).json()
d9 = httpx.post("https://api.navamsha.in/api/v1/divisional/d9", headers=headers, json=birth).json()

print("D1 Moon sign:", d1["output"]["planets"]["Moon"]["zodiac_sign_name"])
print("D9 placements:", d9["output"]["planets"])

Need all sixteen vargas? Use /divisional/shodashvarga for batch divisional output. Full chart documentation lives at /apis/kundali — 10,000 free calls/month, sub-50ms on lightweight endpoints.