AstroWay/api v2.95.1 · astrology-api
all systems operational
// astrology api · POST /v1/vedic/dashas/vimshottari/maha

Vimshottari Mahadasha API

Vimshottari is the 120-year planetary-period cycle that anchors Vedic timing. This endpoint reads the sidereal Moon's position at birth, locates the nakshatra it occupies, and from that single point unrolls the ordered chain of Mahadashas — the major life periods, each governed by one of the nine grahas — with the exact calendar dates that bound them.

Endpoint
POST /v1/vedic/dashas/vimshottari/maha
Cost
50 credits
Latency
~62 ms
Tier
Tier 3
// 01 / What it computes

Vimshottari Mahadasha API

The endpoint converts the birth date, clock time, and UTC offset to a Julian day, then queries the Swiss Ephemeris for the Moon's geocentric longitude and applies the Lahiri ayanamsa to shift it from the tropical to the sidereal zodiac. That sidereal longitude fixes the natal nakshatra and the fraction already elapsed within it, which determines how much of the first ruling planet's period remains at birth. From there it lays out the full 120-year Vimshottari sequence in canonical order — Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury — each Mahadasha carrying its allotted span and concrete start and end dates. The response also returns the birth nakshatra, the Moon's sidereal longitude, and the ayanamsa value used, so the timeline is fully auditable.

// 02 / Live request

POST/v1/vedic/dashas/vimshottari/maha

curl -X POST https://api.astroway.info/v1/vedic/dashas/vimshottari/maha \
  -H "X-Api-Key: aw_live_..." \
  -H "Content-Type: application/json" \
  -d '{
  "date": "1990-05-15",
  "time": "14:30:00",
  "timezoneOffset": 3,
  "latitude": 50.45,
  "longitude": 30.52
}'
Response (excerpt)
{
  "ok": true,
  "data": {
    "system": "vimshottari",
    "level": "maha",
    "ayanamsa": 23.85,
    "moonSiderealLongitude": 258.97,
    "nakshatra": "Purva Ashadha",
    "periods": [
      {
        "lord": "Venus",
        "start": "1986-02-11",
        "end": "2006-02-11"
      },
      {
        "lord": "Sun",
        "start": "2006-02-11",
        "end": "2012-02-11"
      }
    ]
  }
}
// 03 / Parameters

Parameters

nametypeRequired
date string (YYYY-MM-DD) yes Birth date.
time string (HH:MM:SS) yes Local clock time at birth.
timezoneOffset number (hours) yes UTC offset in effect at the birth moment (e.g. 3 for Kyiv summer time). Decimal allowed for half-hour zones.
latitude number yes Birth-place latitude, decimal degrees (north positive).
longitude number yes Birth-place longitude, decimal degrees (east positive).
// 04 / When to use it

When to use it

Use this endpoint when you need the top-level dasha skeleton — the macro periods that frame a person's life chapters — rather than the day-level detail. It is the natural first call for a predictive timeline: render the sequence of major periods, highlight which one is currently active for a given date, and let users drill from there. Because the whole chain follows deterministically from one Moon position, you can compute it once at sign-up and cache it indefinitely. When you need the nested sub-periods inside a given Mahadasha, branch to the dedicated antardasha, pratyantar, sookshma, and prana endpoints under the same Vimshottari family.

// 05 / Notes

Notes

This route returns only the Mahadasha (major-period) layer. The finer subdivisions — antardasha, pratyantar, sookshma, and prana — live at separate endpoints under /v1/vedic/dashas/vimshottari/*. Calculation follows the Parashara tradition as codified in the Bṛhat Parāśara Horā Śāstra, with the sidereal zodiac and the Lahiri ayanamsa as the default reference frame.

Try the Vimshottari Mahadasha API

Grab a key and make your first call in under a minute.

99.9% SLA · paid plans · 30d status →