SEARCH ASTRO INSIGHT API DOCS
The Varshaphal Vim Muddha Dasha API provides Varshaphal 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/varshaphal/vim-muddha-dasha
en
hi
ma
Methodology and astrological context for Varshaphal Vim Muddha Dasha.
Returns the Vimshottari Muddha Dasha (annual sub-period) timeline for a given Varshaphal (Solar Return) year — a planetary period system adapted from the natal Vimshottari Dasha framework and applied within the compressed one-year span of the Tajika annual horoscope. The Vim Muddha Dasha divides the Varshaphal year into sequential planetary sub-periods, each governed by a specific planet, and is one of the primary timing tools used in Varshaphal analysis to pinpoint when during the year particular events or themes are most likely to manifest.
This endpoint accepts the individual's birth details, their current geographic location for the target year, and the desired Varshaphal year, then computes the complete Vimshottari Muddha Dasha sequence for that year. The Muddha Dasha system applies the Vimshottari proportional scheme — the same planetary sequence and relative time allocations used in the natal dasha system — but compresses the entire 120-year cycle into a single solar year. The starting point of the sequence is determined by the Moon's nakshatra position in the Varshaphal chart, and each planetary sub-period (Muddha) runs for a proportional fraction of the year. The endpoint returns the full sequence of Muddha periods with their precise start and end dates, enabling practitioners to map planetary influences onto specific calendar windows within the target year.
The response provides the complete Vim Muddha Dasha breakdown for the target Varshaphal year:
Full Muddha Dasha sequence — the ordered list of all planetary sub-periods active during the target year, following the Vimshottari sequence from the starting planet determined by the Varshaphal Moon's nakshatra
Period start and end dates — precise calendar dates (and optionally times) marking the beginning and end of each Muddha Dasha sub-period within the year
Period duration — the length of each sub-period expressed in days, reflecting the Vimshottari proportional allocation compressed into the annual timeframe
Ruling planet identity — the planet governing each Muddha Dasha sub-period, along with its position, condition, and strength in the Varshaphal chart
Nakshatra reference — the Varshaphal Moon's nakshatra and its balance at the start of the solar return year, which determines the entry point into the Vimshottari sequence
Period significance indicators — summary assessments of each sub-period's likely tone based on the ruling planet's condition, house placement, and strength in the Varshaphal chart
Annual timing and event prediction — identifying the specific calendar windows within the Varshaphal year when particular planetary influences are active, enabling more precise event timing than house or yoga analysis alone
Jyotish practitioners specializing in Tajika — generating the Muddha Dasha timeline as a core component of a complete Varshaphal reading, used to answer when during the year the chart's promises are most likely to manifest
Astrology platforms and apps — powering annual forecast timeline features that display a month-by-month or period-by-period breakdown of planetary influences throughout the year
Integration with Varshaphal yogas and Muntha — combining Muddha Dasha periods with active Tajika yogas and Muntha house placement to identify the most significant windows of the year — periods when strong yogas are activated by a favorable dasha lord
Mudda Dasha lord analysis — using the ruling planet's Varshaphal chart condition (Panchavargeeya Bala, Harsha Bala, house placement) to assess the quality of each sub-period and refine predictions accordingly
Multi-year planning — running the endpoint across consecutive Varshaphal years to map out dasha sequences and identify recurring or shifting planetary period patterns over time
Computes the complete Vimshottari Muddha Dasha sequence for the entire target year, not just the currently active period, providing the full annual timeline in a single response
Determines the dasha entry point from the Varshaphal Moon's nakshatra and its balance at the solar return moment, ensuring the sequence is correctly anchored to the specific Varshaphal chart rather than the natal chart
Returns precise start and end dates for each Muddha sub-period, enabling direct mapping of planetary periods onto the calendar for event timing and forecasting
Evaluates the ruling planet's condition in the Varshaphal chart for each sub-period — including its house placement, sign dignity, and strength scores — providing the interpretive context needed to assess each period's likely quality
Accepts both birth location and current location separately — birth data establishes the natal reference and Varshaphal Moon position, while current latitude, longitude, and timezone determine the Varshaphal ascendant and house framework
Accepts a target Varshaphal year (varshaphalYear) to compute the Muddha Dasha timeline for any past, present, or future solar return year, enabling historical review and multi-year planning
Supports multiple Ayanamsha systems (e.g., Lahiri, Raman, KP) via the X-Ayanamsha header for sidereal calculations aligned with the practitioner's tradition, since the Moon's nakshatra position — and therefore the dasha sequence — varies by Ayanamsha
Designed for localization — the Accept-Language header controls the language of descriptive and interpretive content in the response
Serves as the primary timing layer within a complete Varshaphal analysis, intended to be used alongside planetary position, Muntha, Panchavargeeya Bala, Harsha Bala, and yoga endpoints to answer not just what the year holds but when those influences are most likely to be felt
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
|
|
varshaphalYear
Optional
|
integer |
Varshaphal year.
Example:
2025
|
|
cLat
Required
|
float |
Current Latitude of the birth location.
Example:
28.6139
|
|
cLon
Required
|
float |
Current Longitude of the birth location.
Example:
77.1025
|
|
cTzone
Optional
|
float |
Current 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 Varshaphal Vim Muddha Dasha.
The Varshaphal Vim Muddha Dasha API provides authentic Varshaphal 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 Varshaphal Vim Muddha 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 Varshaphal Vim Muddha Dasha consumes 1 API credit. The endpoint delivers high performance with an average response time of ~78ms.
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.