Logo

SEARCH ASTRO INSIGHT API DOCS

Home Vedic Astrology
POST Vedic API v1

Current Vimshottari Dasha By Date

The Current Vimshottari Dasha By Date 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/current-dasha-by-date
Credit Cost
1 Credit
Avg Latency
~38ms
Auth Type
Basic Auth
Format
JSON / UTF-8

Available Response Languages

🇬🇧 English en
🇮🇳 Hindi hi
🇮🇳 Marathi ma

API Overview & Calculation Details

Methodology and astrological context for Current Vimshottari Dasha By Date.

Current Vimshottari Dasha By Date

Returns the complete active Vimshottari Dasha state for a given natal chart at a caller-specified target date — a date-parameterized variant of the Current Vimshottari Dasha endpoint that resolves all five levels of the Vimshottari hierarchy simultaneously for any arbitrary past, present, or future date rather than being fixed to the server's current moment. This endpoint is the most flexible entry point for dasha state lookups, enabling historical analysis, future planning, and date-specific dasha snapshots without navigating the full hierarchy level by level.

What This API Does

This endpoint accepts an individual's birth details along with a target date (cDay, cMonth, cYear) supplied in the request body, and computes the active dasha period at every level of the Vimshottari hierarchy as of that specified date. It resolves the single active period at each of the five levels — Mahadasha, Antardasha, Pratyantardasha, Sookshma Dasha, and Pran Dasha — for the given target date and returns them together as a unified dasha snapshot anchored to that date. It also evaluates the natal chart condition of each active dasha lord and the inter-lord relationships across all active levels, providing the full interpretive context needed to assess the quality and themes of the planetary period stack on the specified date.

Data Returned

The response provides the full active Vimshottari Dasha stack as of the specified target date:

  • Active Mahadasha — the major period running on the target date, including the governing planet, its natal position and condition, and the Mahadasha's start and end dates

  • Active Antardasha — the sub-period running on the target date within the active Mahadasha, including the governing planet, its natal position and condition, and the Antardasha's start and end dates

  • Active Pratyantardasha — the sub-sub-period running on the target date within the active Antardasha, including the governing planet, its natal position and condition, and the Pratyantardasha's start and end dates

  • Active Sookshma Dasha — the sub-sub-sub-period running on the target date within the active Pratyantardasha, including the governing planet, its natal position and condition, and the Sookshma Dasha's start and end dates

  • Active Pran Dasha — the sub-sub-sub-sub-period running on the target date within the active Sookshma Dasha, including the governing planet, its natal position and condition, and the Pran Dasha's precise start and end timestamps

  • Inter-lord relationship assessments — evaluations of the mutual relationships between all active dasha lords across the five levels on the target date, highlighting harmonious and conflicting planetary combinations in the period stack

  • Dasha lord natal positions — the zodiac sign, degree, house placement, nakshatra, and dignity of each active dasha lord in the natal chart

  • Period remaining from target date — the time remaining in each active period at every level as of the specified target date, giving an immediate sense of how far into each period the individual is on that date and when the next transition at each level will occur

Main Use Cases

  • Future dasha planning — determining the complete dasha stack that will be active on a specific future date, enabling practitioners and clients to understand the planetary period context for upcoming life events, decisions, or milestones

  • Historical event analysis — resolving the full dasha stack that was active on a specific past date to correlate life events with the planetary periods running at the time, deepening interpretive understanding and validating the dasha system

  • Jyotish practitioners — quickly establishing the dasha context for any date a client asks about — past, present, or future — without navigating the full hierarchy or manually calculating which periods were active on that date

  • Astrology platforms and apps — powering date-picker dasha lookup features that allow users to select any date on a calendar and instantly see the complete five-level dasha stack active on that day

  • Dasha transition planning — checking the dasha state on specific upcoming dates to identify when major transitions at any level will occur, helping clients plan around significant period changes

  • Compatibility and synastry timing — resolving the dasha states of two individuals on the same target date to compare their concurrent planetary period stacks as part of relationship timing analysis

  • Automated report generation — providing the dasha state for any specified date as a structured data input for report generation pipelines that need period context for a particular date rather than the current moment

Key Functionality

  • Accepts a caller-specified target date (cDay, cMonth, cYear) in the request body, enabling dasha state resolution for any past, present, or future date — the key differentiator from the Current Vimshottari Dasha endpoint, which is fixed to the server's current moment

  • Resolves the complete five-level active dasha stack for the target date in a single request — Mahadasha, Antardasha, Pratyantardasha, Sookshma, and Pran — eliminating the need for five sequential endpoint calls

  • Returns only the active period at each level on the specified date rather than full sequences, keeping the response compact and immediately actionable

  • Includes period remaining from the target date at every level, providing transition timing data relative to the specified date rather than the current moment — useful for planning and historical analysis alike

  • Evaluates inter-lord relationships across all five active levels simultaneously for the target date, giving a holistic picture of the dasha stack's internal harmony or tension

  • Returns natal chart context for every active dasha lord — sign, house, dignity, and nakshatra — so the date-specific dasha snapshot is fully interpretively enriched

  • Accepts birth details plus a target date in the request body with no path parameters required, keeping the interface simple while supporting the full range of date-specific lookups

  • Supports multiple Ayanamsha systems (e.g., Lahiri, Raman, KP) via the X-Ayanamsha header, since the Moon's nakshatra position — and therefore the entire dasha timeline — varies 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 date-flexible complement to the Current Vimshottari Dasha endpoint — use Current Vimshottari Dasha for real-time snapshots and this endpoint whenever the target date needs to be explicitly controlled, whether for past analysis, future planning, or any date other than the present moment

 

Request Parameters

Payload specifications for JSON request body.

application/json
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

Required & Optional Headers

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

Frequently Asked Questions

Comprehensive developer guidance for Current Vimshottari Dasha By Date.

What is the Current Vimshottari Dasha By Date API and what data does it provide?

The Current Vimshottari Dasha By Date 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.

What input parameters are required to call Current Vimshottari Dasha By Date?

The Current Vimshottari Dasha By Date 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.

How many credits does the Current Vimshottari Dasha By Date endpoint consume?

Each calculation request to Current Vimshottari Dasha By Date consumes 1 API credit. The endpoint delivers high performance with an average response time of ~38ms.

How do I authenticate with the Current Vimshottari Dasha By Date API?

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)).

Can I get Current Vimshottari Dasha By Date responses in regional Indian languages?

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.

Which Ayanamsha systems can be calculated with Current Vimshottari Dasha By Date?

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.

What response format and HTTP codes does this API return?

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.

POST dasha/vimshottari/current-dasha-by-date
Presets:
Live Output
Click Send above to execute calculation.
Sample Output

API Categories