SEARCH ASTRO INSIGHT API DOCS
The Antar Vimshottari Dasha API provides Vimshottari Dasha related calculations and insights based on Vedic Astrology principles. This endpoint is designed for astrology applications, report generation systems, horoscope platforms, and developer integrations requiring structured JSON responses and reliable REST API access.
https://json.astroinsightapi.com/api/v1/dasha/vimshottari/antar-dasha/:majorDashaKey
en
hi
ma
Methodology and astrological context for Antar Vimshottari Dasha.
Returns the complete sequence of Antardasha (sub-period) divisions within a specified Vimshottari Mahadasha (major period) for a given natal chart — the second level of the Vimshottari Dasha hierarchy. Each Mahadasha is subdivided into nine Antardashas, one for each planet in the Vimshottari sequence, with durations proportional to both the Mahadasha lord's total period length and each sub-lord's standard Vimshottari allocation. The Antardasha level is where most day-to-day predictive work in Jyotish is conducted, as it narrows the broad themes of a Mahadasha down to specific multi-month windows governed by a secondary planetary influence.
This endpoint accepts an individual's birth details and a path parameter specifying the Mahadasha lord (majorDashaKey), then computes the complete Antardasha breakdown within that Mahadasha. It calculates the precise start and end dates of all nine Antardasha sub-periods within the specified major period, ordered according to the Vimshottari sequence starting from the Mahadasha lord itself. The endpoint also evaluates the natal chart condition of each Antardasha lord and assesses the relationship between the Mahadasha lord and each Antardasha lord — a key interpretive factor in determining whether a given sub-period is likely to be harmonious, challenging, or mixed in its effects.
The response provides the complete Antardasha breakdown for the specified Mahadasha:
Full Antardasha sequence — the ordered list of all nine sub-periods within the specified Mahadasha, following the Vimshottari sequence starting from the Mahadasha lord
Period start and end dates — precise calendar dates marking the beginning and end of each Antardasha sub-period
Period duration — the length of each Antardasha in days and months, calculated proportionally from the Mahadasha lord's total period length and each sub-lord's Vimshottari allocation
Mahadasha lord context — the identity, natal position, house placement, dignity, and strength of the governing Mahadasha lord, providing the overarching context within which all Antardashas operate
Antardasha lord identity and natal position — the planet governing each sub-period, along with its zodiac sign, degree, house placement, nakshatra, and dignity in the natal chart
Inter-lord relationship assessment — an evaluation of the relationship between the Mahadasha lord and each Antardasha lord (e.g., mutual friends, enemies, neutral), which is a primary determinant of whether the sub-period amplifies or complicates the Mahadasha's themes
Currently active Antardasha — identification of which sub-period is currently active within the specified Mahadasha, if the Mahadasha itself is currently running
Sub-period significance indicators — summary assessments of each Antardasha's likely tone based on the sub-lord's natal condition and its relationship with the Mahadasha lord
Precise event timing within a Mahadasha — narrowing the broad themes of a major planetary period down to specific multi-month windows by identifying which Antardasha is active during a given calendar period, enabling more targeted predictions than Mahadasha analysis alone
Jyotish practitioners — drilling into the sub-period structure of the current or upcoming Mahadasha to provide clients with a detailed timeline of shifting planetary influences within their major life chapter
Astrology platforms and apps — powering dasha timeline features that display the Antardasha breakdown within a selected Mahadasha, allowing users to explore the sub-period structure of any major period in their natal chart
Current sub-period identification — quickly determining which Antardasha a person is currently running within their active Mahadasha, as a prerequisite for deeper analysis using Pratyantardasha (sub-sub-period) endpoints
Inter-lord compatibility analysis — using the Mahadasha–Antardasha lord relationship data to identify sub-periods that are likely to be particularly favorable or challenging based on planetary friendships and enmities
Life event correlation — mapping significant past events onto the Antardasha timeline to validate sub-period themes and refine interpretive frameworks before applying them to future predictions
Transition period planning — identifying upcoming Antardasha transitions and the nature of the incoming sub-lord to help clients prepare for shifts in the dominant planetary influence within their current major period
Accepts a majorDashaKey path parameter specifying the Mahadasha lord (sun, moon, mars, mercury, jupiter, venus, saturn, rahu, or ketu), enabling targeted retrieval of the Antardasha breakdown for any of the nine possible Mahadashas without requiring the caller to first fetch the full Mahadasha timeline
Computes all nine Antardasha sub-periods within the specified Mahadasha in a single response, providing the complete sub-period timeline rather than only the currently active or near-term sub-periods
Calculates precise start and end dates for each Antardasha using the standard Vimshottari proportional formula, anchored to the individual's birth-determined Mahadasha start date
Evaluates the inter-lord relationship between the Mahadasha lord and each Antardasha lord — one of the most practically important interpretive data points at this level — and includes it directly in the response to support immediate qualitative assessment
Identifies the currently active Antardasha within the specified Mahadasha (when that Mahadasha is currently running), providing an immediate practical reference point
Returns natal chart context for each Antardasha lord — including sign, house, dignity, and nakshatra — so the sub-period timeline is interpretively enriched rather than being a bare list of dates
Accepts only birth details (date, time, and place of birth) with no current location required, since Antardasha calculation is based entirely on the natal chart
Supports multiple Ayanamsha systems (e.g., Lahiri, Raman, KP) via the X-Ayanamsha header, since planetary positions and nakshatra placements vary by sidereal reference frame
Designed for localization — the Accept-Language header controls the language of planet names, nakshatra names, relationship labels, and all descriptive content in the response
Serves as the second level of the Vimshottari Dasha hierarchy, intended to be used after the Major Vimshottari Dasha endpoint has identified the relevant Mahadasha, and before the Pratyantardasha endpoint for further sub-division into finer timing windows
Payload specifications for JSON request body.
| Parameter | Type | Description & Example |
|---|---|---|
|
day
Required
|
integer |
Day of birth (1–31).
Example:
15
|
|
month
Required
|
integer |
Month of birth (1–12).
Example:
9
|
|
year
Required
|
integer |
Year of birth (e.g., 1994).
Example:
1994
|
|
hour
Required
|
integer |
Hour of birth in 24-hour format (0–23).
Example:
12
|
|
min
Required
|
integer |
Minute of birth (0–59).
Example:
30
|
|
sec
Optional
|
integer |
Second of birth (0–59). Optional. If not provided, it is considered as 0.
Example:
30
|
|
lat
Required
|
float |
Latitude of the birth location.
Example:
28.6139
|
|
lon
Required
|
float |
Longitude of the birth location.
Example:
77.1025
|
|
tzone
Optional
|
float |
Timezone offset from UTC. Optional. If not provided, it is considered as 5.5 (IST).
Example:
5.5
|
| Header Key | Value / Format | Description |
|---|---|---|
|
Authorization
Required
|
Basic {base64} |
Base64 encoded string of CLIENT_ID:CLIENT_SECRET. |
|
Content-Type
Required
|
application/json |
Specifies JSON payload format in request body. |
|
Accept-Language
Optional
|
en, hi, ta, te... |
Returns localized astrology output. Default: en |
|
X-Ayanamsha
Optional
|
lahiri, raman, krishnamurti... |
Ayanamsha system: lahiri, raman, fagan_bradley, usha_shashi, krishnamurti, djwhal_khul, yukteshwar, jn_bhasin, suryasiddhanta, aryabhata. Default: lahiri |
Explore complementary endpoints in this category.
Comprehensive developer guidance for Antar Vimshottari Dasha.
The Antar Vimshottari Dasha API provides authentic Vimshottari Dasha calculations based on Vedic astrology algorithms. It returns structured JSON data containing detailed planetary positions, house calculations, and astrological parameters suitable for Kundli apps, astrology websites, and developer applications.
The Antar Vimshottari Dasha API requires standard Vedic birth details: day, month, year, hour, min, sec, latitude (lat), longitude (lon), and timezone (tzone). All parameters can be passed in the JSON request body.
Each calculation request to Antar Vimshottari Dasha consumes 1 API credit. The endpoint delivers high performance with an average response time of ~69ms.
Authenticate using HTTP Basic Authentication by including your Base64 encoded client_id:client_secret credentials in the Authorization header (Authorization: Basic BASE64(client_id:client_secret)).
Yes! The API supports multiple languages including English, Hindi, Marathi. Pass your desired language code (e.g. 'hi' for Hindi, 'ta' for Tamil, 'en' for English) in the Accept-Language request header.
Supported Ayanamshas include NC Lahiri (Default), BV Raman, Krishnamurti (KP), Fagan Bradley, Usha Shashi, Djwhal Khul, Sri Yukteshwar, JN Bhasin, Surya Siddhanta, and Aryabhata. Specify your choice using the X-Ayanamsha header.
The API returns clean JSON UTF-8 output. Successful requests return HTTP 200 OK with the computed data payload. Parameter validation errors return HTTP 422 with actionable error messages.