Skip to content
Kundali & Planets API

Lightning-fast birth chart and planetary position APIs

Build Kundli generators, profile charts, and planet dashboards with deterministic Lahiri ayanamsa calculations. Every response includes engine metadata for audit and validation.

Why developers choose Navamsha for Kundali APIs

Building a Janam Kundli feature in-house means licensing ephemeris software, handling timezone edge cases, choosing an ayanamsa convention, and maintaining golden fixtures whenever you ship a new release. Navamsha wraps Swiss Ephemeris astronomy with deterministic Lahiri sidereal logic so your team integrates via REST instead of maintaining C libraries or Python ephemeris bindings in production.

Every Kundali response includes engine metadata — ayanamsa, node mode, house system, formula version — which makes customer support tractable. When a user disputes a chart placement, you can point to stamped calculation context rather than guessing whether your app and a pandit's software used the same conventions.

Integration patterns that scale

Most production apps call /api/v1/kundali/basic once per user profile and cache the JSON by a hash of birth inputs. Heavier flows — divisional charts, extended planetary dignities, or batch family charts — use dedicated endpoints so you only pay the credit cost when you need the extra fields. Server-side fetching keeps your API key off client devices.

Navamsha powers Astro Vedica's live Kundli flows, which means the same endpoints you integrate during development are exercised under real user traffic. During launch, the free tier includes 10,000 calls per month with no credit card — enough to prototype, run QA, and soft-launch without a billing integration.

Accuracy, validation, and conventions

Lahiri ayanamsa is the default — the convention most contemporary Vedic software uses in India. If your product targets users who expect Raman or KP charts, document the difference clearly; Navamsha's metadata makes the active ayanamsa explicit on every response so downstream AI or report generators do not silently mislabel positions.

For lagna-sensitive applications, pass topocentric observation settings and precise birth time. Even a few minutes can shift the ascendant border in borderline cases. Pair chart output with your own golden fixtures during migration; Navamsha's deterministic outputs are designed for automated regression tests, not one-off manual checks.

Example endpoints

GET/api/v1/kundali/basic

Core birth chart snapshot

1 credit / call
GET/api/v1/planets/extended

Extended planetary positions

1 credit / call
GET/api/v1/houses/whole-sign

Whole-sign house cusps

1 credit / call

What you can build

Kundli generator apps

Render Janam Kundli PDFs and interactive charts from a single GET call. Pair with divisional chart endpoints for D9 Navamsha views.

Astrologer CRM dashboards

Pre-compute client charts server-side and cache by birth hash. Extended planets endpoint adds retrograde, combustion, and dignity flags.

AI astrologer grounding

Fetch deterministic chart JSON before LLM inference so your chatbot cites real planetary positions instead of hallucinating placements.

How it works

  1. 1

    Send birth datetime, latitude, longitude, and timezone with your API key in the X-API-Key header.

  2. 2

    Navamsha converts local time to UTC, resolves timezone if needed, and runs Swiss Ephemeris for tropical positions.

  3. 3

    Lahiri ayanamsa is applied to produce sidereal longitudes, lagna, whole-sign houses, and Nakshatra assignments.

  4. 4

    Every response includes engine metadata — ayanamsa, node mode, house system — for audit and golden-fixture validation.

Sample request / response

Request

curl -G "https://api.navamsha.in/api/v1/kundali/basic" \
  -H "X-API-Key: YOUR_API_KEY" \
  --data-urlencode "year=1995" \
  --data-urlencode "month=8" \
  --data-urlencode "date=15" \
  --data-urlencode "hours=14" \
  --data-urlencode "minutes=30" \
  --data-urlencode "latitude=19.0760" \
  --data-urlencode "longitude=72.8777" \
  --data-urlencode "timezone=5.5"

Response (abbreviated)

{
  "lagna": { "sign": "Scorpio", "degree": 12.45 },
  "planets": [
    { "name": "Sun", "sign": "Leo", "house": 10, "nakshatra": "Magha" },
    { "name": "Moon", "sign": "Aquarius", "house": 4, "nakshatra": "Shatabhisha" }
  ],
  "metadata": {
    "engine": "swiss_ephemeris",
    "ayanamsa": "lahiri",
    "house_system": "whole_sign"
  }
}

Built for

    Kundli apps

    Astrologer CRM charts

    AI astrologer context layers

FAQ

What is the Kundali API used for?

Generate birth charts (Janam Kundli) with lagna, planetary positions, houses, and Nakshatra data for mobile apps, web Kundli tools, and AI astrologer backends.

What ayanamsa does Navamsha use?

Lahiri ayanamsa by default — the most common standard in contemporary Vedic astrology software. Engine metadata is returned on every response.

Is there a free tier?

Yes — 10,000 API calls per month during launch, no credit card required. Sign up at www.navamsha.in/auth/signup.

How fast are Kundali API responses?

Sub-50ms average latency on lightweight chart endpoints, backed by Swiss Ephemeris runtime calculations and optimized API infrastructure.

Can I request divisional charts (D9, D10)?

Divisional chart endpoints are available in the extended catalog. Start with /api/v1/kundali/basic for D1 and explore divisional routes in Swagger.

What birth time format is supported?

Pass year, month, date, hours, minutes, and seconds as separate query parameters or JSON fields. Use 24-hour local time with an explicit timezone offset.

Does the API support topocentric vs geocentric?

Yes — set observation_point in settings. Topocentric is recommended for lagna-accurate charts at the birth location.