Skip to content
Dasha & Timing API

Vimshottari, Yogini, and deterministic Dasha engines

Expose Vimshottari timelines with source-stamped formulas. Ideal for Dasha explainers, transit overlays, and period-based notifications.

Vimshottari and timing APIs without local ephemeris

Dasha timelines drive predictive features — notifications when Antardasha changes, AI astrologer context about active lords, and coaching dashboards that overlay life periods on calendars. Computing Vimshottari from scratch requires accurate Moon longitude at birth, Nakshatra assignment, and balance-of-Dasha arithmetic tied to your chosen ayanamsa.

Navamsha exposes full Vimshottari trees and lightweight 'current period' lookups so you fetch only the depth your UX needs. Yogini and related systems live in sibling endpoints for products that support multiple timing traditions without duplicating vendor integrations.

Product use cases for Dasha data

AI astrologer products should attach active Mahadasha and Antardasha lords to every interpretive prompt — grounded on JSON from /api/v1/dasha/current rather than LLM guesses. Life-event apps can schedule push notifications when sub-periods change by polling periodically and diffing results.

Educational products render interactive Dasha charts by fetching the full tree once, caching it client-side, and highlighting the active slice. Because responses include formula and engine metadata, your content team can explain why a period boundary falls on a specific date when users ask.

Birth time sensitivity and validation

Dasha balance at birth depends on precise Moon longitude. Collect birth time to the minute — ideally with AM/PM confirmation in UX — and store timezone explicitly. Borderline Nakshatra cases are where API accuracy reviews matter most; run golden births through your pipeline before launch.

Combine Dasha endpoints with Kundali routes from the same platform so ayanamsa and node conventions stay consistent across chart and timing features. Mixed vendors often disagree on period boundaries for the same birth data; single-vendor JSON reduces support burden.

Example endpoints

GET/api/v1/dasha/vimshottari

Full Vimshottari tree

2 credit / call
GET/api/v1/dasha/current

Active Mahadasha / Antardasha

1 credit / call
GET/api/v1/dasha/yogini

Yogini Dasha periods

2 credit / call

What you can build

Life coaching timelines

Overlay Dasha periods on user dashboards and send push notifications when Antardasha lords change.

AI timing assistants

Ground LLM responses with the active Mahadasha lord and sub-period dates so predictions reference real timing windows.

Dasha explainer products

Fetch the full Vimshottari tree once, cache it, and render interactive period charts without recomputing ephemeris math.

How it works

  1. 1

    Birth Moon longitude determines Nakshatra and the starting Mahadasha lord with remaining balance at birth.

  2. 2

    The 120-year Vimshottari cycle is computed from graha period tables — deterministic and source-stamped in metadata.

  3. 3

    Current Dasha endpoint resolves active Mahadasha and Antardasha for any target date without returning the full tree.

  4. 4

    Yogini and Ashtottari systems are available as separate endpoint families for apps supporting multiple Dasha traditions.

Sample request / response

Request

curl -G "https://api.navamsha.in/api/v1/dasha/vimshottari" \
  -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)

{
  "birth_nakshatra": "Shatabhisha",
  "balance_at_birth": { "lord": "Rahu", "years_remaining": 15.2 },
  "mahadashas": [
    { "lord": "Rahu", "start": "1995-08-15", "end": "2013-04-22" },
    { "lord": "Jupiter", "start": "2013-04-22", "end": "2029-04-22" }
  ],
  "metadata": { "system": "vimshottari", "ayanamsa": "lahiri" }
}

Built for

    AI timing assistants

    Life coaching apps

    Dasha notification products

FAQ

What is the Dasha API used for?

Vimshottari Mahadasha and Antardasha timelines, current period lookups, and Yogini Dasha — for predictive apps, AI astrologers, and life-event notifications.

What ayanamsa does Navamsha use?

Lahiri ayanamsa. The Moon's sidereal longitude determines birth Nakshatra and the Vimshottari balance calculation — ayanamsa choice directly affects Dasha timing.

Is there a free tier?

Yes — 10,000 calls/month free during launch. Dasha endpoints typically cost 1–2 credits per call depending on depth.

How fast are Dasha API responses?

Current Dasha lookups are fast; full Vimshottari trees are heavier but still optimized for production dashboards and chat context layers.

How does birth time accuracy affect Dasha?

Dasha balance depends on exact Moon longitude. Even a few minutes can shift Nakshatra pada and the balance calculation — always collect precise birth time.

Can I query Dasha for a specific date?

Yes — use /api/v1/dasha/current with a target_date parameter to get the active Mahadasha and Antardasha on that day.

Are Antardashas included in the full tree?

The Vimshottari endpoint returns Mahadasha periods. Nested Antardasha/pratyantardasha depth varies by endpoint — see Swagger for the full schema.