The Five Levels of Vimshottari Dasha, and Why Most APIs Stop at Two

A practitioner reviewing a Dasha-based prediction is not working with a single time window. They are working with five nested windows simultaneously. The question is never just "what Mahadasha is this person in?" It is "what is the specific combination of all five lords active at this exact moment, and what does that combination signify?"

An API that returns Mahadasha and Antardasha answers the first two parts of that question. The practitioner still needs to do the remaining three calculations by hand, or rely on separate software, or accept that the timing resolution of the application stops at a level that is too coarse for the question being asked.

This post describes what the five levels are, what each level is used for in classical practice, and what the actual date ranges look like when all five are computed from a real chart.

The Five Levels and What They Are Called

The Vimshottari system assigns each of the nine Grahas a period of years adding to 120 in total. The sequence runs from the Moon's birth Nakshatra and produces a Mahadasha for each Graha in order. Within each Mahadasha, the same nine Grahas rule proportional sub-periods. Within each sub-period, another proportional subdivision. This nesting continues for five levels.

The five levels have classical names. Mahadasha is the outer period, spanning multiple years. Antardasha is the sub-period within it, spanning months to a few years. Pratyantar Dasha is the third level, spanning weeks to a few months. Sookshma Dasha is the fourth level, spanning days to a few weeks. Prana Dasha is the fifth and innermost level, spanning hours to a few days. At the Prana level, the sub field in the API response is null - there is no sixth level.

The proportion between levels is fixed. Each level is a proportional slice of the level above it, using the same 120-year Vimshottari ratios applied recursively. A 17-year Mahadasha contains Antardashas ranging from roughly 10 months to just over 3 years. Each of those Antardashas contains Pratyantars ranging from a few weeks to a few months. And so on until Prana, where the period is measured in days.

What Each Level Is Used For

Mahadasha sets the broad thematic context of a life phase. A practitioner reading a Mercury Mahadasha spanning 17 years is describing a period where Mercury's significations - communication, commerce, analysis, adaptability - govern the general direction of that phase. The Mahadasha alone cannot predict a specific event. It defines the terrain.

Antardasha narrows the terrain to a specific sub-theme. The planet ruling the Antardasha introduces its own significations into the Mercury period. Ketu Antardasha within Mercury Mahadasha produces a specific intersection of Mercury and Ketu qualities that is different from Jupiter Antardasha within the same Mercury Mahadasha. Practitioners use Antardasha to identify phases within the larger period where specific domains of life become active.

Pratyantar Dasha narrows further to roughly seasonal resolution. This is where event-level timing begins to become possible in classical practice. A practitioner looking for the most likely window for a specific event - a relocation, a change of role, a significant relationship development - uses Pratyantar to identify the months within an Antardasha where the relevant planetary combination is active.

Sookshma Dasha narrows to week-level resolution. Classical texts use Sookshma for timing within a Pratyantar when a specific event is expected and the practitioner needs to identify the most active window at that finer grain. At this level, the five-planet combination active simultaneously carries significant interpretive weight.

Prana Dasha provides day-level resolution. This is the floor of the Vimshottari system. Classical practitioners rarely use Prana for general prediction, but it is used in specific electional and timing contexts where day-level precision matters.

What the Numbers Look Like in a Real Chart

For a chart born on 12 November 1985 at 06:45 in Mumbai, the current Mahadasha is Mercury, running from 29 April 2023 to 28 April 2040 - a span of 17 years. Within that Mahadasha, the Mercury Antardasha ran from 29 April 2023 to 24 September 2025 - just under two and a half years.

Within that Mercury Antardasha, the first Pratyantar was Mercury, running from 29 April 2023 to 31 August 2023 - four months. Within that Pratyantar, the first Sookshma was Mercury, running from 29 April 2023 to 16 May 2023 - seventeen days. Within that Sookshma, the first Prana was Mercury, running from 29 April 2023 to 01 May 2023 - three days.

These dates are computed from the API with levels=5. The Prana-level response carries sub: null, confirming it is the floor. The full tree from 17 years to 3 days is available in one call.

Why Most APIs Stop at Two

Computing five levels of Vimshottari produces a large response. For a full 120-year tree at five levels, the number of period objects is substantial - nine Mahadashas, each with nine Antardashas, each with nine Pratyantars, each with nine Sookshmas, each with nine Pranas. Most API designs avoid this payload size by capping at two or three levels and treating the deeper levels as an edge case for specialist use.

The consequence is that the depth parameter becomes a paid or specialist feature in most implementations, or is simply not offered. A developer building a timing feature on those APIs has two options: stop at Antardasha and accept the coarser resolution, or implement the Pratyantar and deeper calculations in their own application layer, which requires replicating the proportional Vimshottari arithmetic correctly.

The proportional arithmetic is not complicated to implement, but it does require knowing the exact Mahadasha year-lengths for each planet, computing the proportional slices correctly, and anchoring the calculation to the precise Moon Nakshatra balance at birth. An error in the birth Nakshatra degree propagates into every level below it, making the deeper levels meaningfully wrong for charts where the Moon is near a Nakshatra boundary.

How the Asterwise Response Is Structured

The Asterwise Dasha endpoint accepts a levels parameter from 1 to 5. At levels=1, only Mahadasha objects are returned. At levels=5, the full five-level tree is returned with each period carrying start_date, end_date, and a sub array containing the next level. At the Prana level, sub is null.

The dates at every level are computed from the Moon's exact sidereal longitude at birth, using the Swiss Ephemeris to determine the precise Nakshatra balance remaining at the birth moment. This means the Pratyantar and deeper levels are anchored to the same ephemeris precision as the Mahadasha, not estimated from an approximated balance.

A developer who needs only Mahadasha for a lightweight feature uses levels=1 and receives a small payload. A developer building a precise timing tool uses levels=5 and receives the full tree. The same endpoint serves both use cases without requiring a separate integration for deeper levels.