SEARCH ASTRO INSIGHT API DOCS
The Varshaphal Yogini 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/yogini-muddha-dasha
en
hi
ma
Methodology and astrological context for Varshaphal Yogini Muddha Dasha.
Returns the Yogini Muddha Dasha (annual sub-period) timeline for a given Varshaphal (Solar Return) year — a planetary period system based on the Yogini Dasha framework, adapted and compressed into the one-year span of the Tajika annual horoscope. The Yogini Muddha Dasha offers an alternative timing perspective to the Vimshottari Muddha Dasha, associating each sub-period with one of eight Yoginis (each linked to a specific planet) and providing a complementary lens through which to time events and assess planetary influences across the target year.
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 Yogini Muddha Dasha sequence for that year. The Yogini Dasha system uses a fixed 36-year cycle governed by eight Yoginis — Mangala, Pingala, Dhanya, Bhramari, Bhadrika, Ulka, Siddha, and Sankata — each associated with a ruling planet and assigned a specific number of years in the full cycle. When compressed into the Varshaphal annual framework, these proportional allocations translate into sub-periods of varying lengths within the single solar year. The starting Yogini is determined by the Moon's nakshatra in the Varshaphal chart, and the sequence proceeds through the eight Yoginis in order from that entry point. The endpoint returns the full sequence of Yogini Muddha periods with their precise start and end dates, enabling practitioners to map Yogini-governed influences onto specific calendar windows within the target year.
The response provides the complete Yogini Muddha Dasha breakdown for the target Varshaphal year:
Full Yogini Muddha Dasha sequence — the ordered list of all Yogini sub-periods active during the target year, following the eight-Yogini cycle from the entry point determined by the Varshaphal Moon's nakshatra
Yogini identity per period — the name of the Yogini governing each sub-period (Mangala, Pingala, Dhanya, Bhramari, Bhadrika, Ulka, Siddha, or Sankata) along with her associated ruling planet
Period start and end dates — precise calendar dates marking the beginning and end of each Yogini Muddha sub-period within the year
Period duration — the length of each sub-period in days, reflecting the Yogini cycle's proportional allocation compressed into the annual timeframe
Ruling planet identity and condition — the planet associated with each Yogini, along with its position, house placement, 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 Yogini sequence
Period significance indicators — summary assessments of each sub-period's likely tone based on the Yogini's nature and the condition of her associated planet in the Varshaphal chart
Annual timing and event prediction — using the Yogini Muddha Dasha as an alternative or complementary timing system to the Vimshottari Muddha Dasha, identifying specific calendar windows within the year when particular Yogini-governed influences are active
Jyotish practitioners specializing in Tajika — generating the Yogini Muddha Dasha timeline as part of a multi-system timing analysis, cross-referencing it with the Vimshottari Muddha Dasha to identify periods where both systems agree on planetary emphasis
Astrology platforms and apps — powering annual forecast timeline features that offer the Yogini Dasha perspective alongside or as an alternative to the Vimshottari system, catering to practitioners who prefer or specialize in Yogini-based timing
Cross-system timing validation — combining Yogini Muddha Dasha periods with Vimshottari Muddha Dasha, Tajika yogas, and Muntha analysis to identify high-confidence timing windows where multiple systems converge on the same planetary influence
Yogini-specific interpretive analysis — leveraging the distinct character and significations of each Yogini (beyond just her ruling planet) to add a layer of qualitative nuance to period interpretations that the Vimshottari system alone does not provide
Multi-year planning — running the endpoint across consecutive Varshaphal years to track Yogini period patterns and identify years where particularly favorable or challenging Yoginis dominate significant portions of the annual timeline
Computes the complete Yogini Muddha Dasha sequence for the entire target year, covering all eight Yoginis in their correct order from the nakshatra-determined entry point, and returning the full annual timeline in a single response
Identifies each sub-period by Yogini name and associated planet, preserving the Yogini system's distinct identity rather than reducing it to a simple planetary period list — the Yogini's own character and significations are part of the interpretive output
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
Returns precise start and end dates for each Yogini Muddha sub-period, enabling direct mapping of Yogini influences onto the calendar for event timing and forecasting
Evaluates the associated planet's condition in the Varshaphal chart for each sub-period — including house placement, sign dignity, and strength scores — providing the interpretive context needed to assess each Yogini 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 Yogini 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 Yogini entry point — varies by Ayanamsha
Designed for localization — the Accept-Language header controls the language of Yogini names, descriptive content, and interpretive text in the response
Serves as a complementary timing layer to the Varshaphal Vim Muddha Dasha endpoint, intended to be used alongside it and other Varshaphal endpoints (planets, Muntha, Panchavargeeya Bala, yogas) to build a multi-system annual timing picture
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 Yogini Muddha Dasha.
The Varshaphal Yogini 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 Yogini 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 Yogini Muddha Dasha consumes 1 API credit. The endpoint delivers high performance with an average response time of ~95ms.
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.