SEARCH ASTRO INSIGHT API DOCS
The Antar Yogini Dasha By Cycle API provides yogini dasha related calculations and insights based on Vedic Astrology astrology data. This endpoint is designed for horoscope platforms, astrology applications, mobile apps, and developer integrations requiring accurate JSON responses and scalable REST API access.
https://json.astroinsightapi.com/api/v1/dasha/yogini/antar-dasha-by-cycle/:dashaCycle/:dashaKey
en
hi
ma
Methodology and astrological context for Antar Yogini Dasha By Cycle.
Returns the Antardasha (sub-period) breakdown for a specific Yogini major period within a specified cycle of the Yogini Dasha system — a targeted variant of the Antar Yogini Dasha endpoint that allows precise retrieval of the sub-period structure for any named Yogini in any particular repetition of the 36-year Yogini Dasha cycle. Since the Yogini Dasha's 36-year cycle repeats multiple times across a person's lifetime, this endpoint enables disambiguation between occurrences of the same Yogini in different cycles, making it the appropriate endpoint when a specific cycle instance of a Yogini period is needed rather than the full two-level timeline.
This endpoint accepts an individual's birth details along with two path parameters — dashaCycle specifying which repetition of the 36-year Yogini cycle (1, 2, or 3) and dashaKey specifying the Yogini by name (mangala, pingala, dhanya, bhramari, bhadrika, ulka, siddha, or sankata) — and computes the complete Antardasha sub-period breakdown for that specific Yogini period occurrence. It calculates the precise start and end dates of all eight Antardasha sub-periods within the specified major Yogini period, ordered according to the Yogini sequence starting from the named Yogini, with durations proportionally derived from the major period's length and each sub-Yogini's standard allocation. The endpoint evaluates the natal chart condition of each sub-period's associated planet and the inter-Yogini planetary relationships, providing the interpretive context needed to assess the quality and themes of each sub-period within the targeted cycle instance.
The response provides the complete Antardasha breakdown for the specified Yogini period in the specified cycle:
Full Antardasha sequence — the ordered list of all eight sub-periods within the specified major Yogini period, following the Yogini sequence starting from the named Yogini (dashaKey)
Cycle and Yogini context — the cycle number (dashaCycle) and the identity of the major Yogini period (dashaKey), along with the major period's start and end dates within that specific cycle occurrence
Yogini identity and associated planet per sub-period — the name of the Yogini governing each Antardasha and her associated ruling planet
Period start and end dates — precise calendar dates marking the beginning and end of each Antardasha sub-period within the specified major Yogini period
Period duration — the length of each Antardasha in days and months, calculated proportionally from the major Yogini period's length in the specified cycle
Associated planet natal position per sub-period — the zodiac sign, degree, house placement, nakshatra, and dignity of each Antardasha Yogini's ruling planet in the natal chart
Inter-Yogini relationship assessment — evaluations of the relationship between the major Yogini's ruling planet and each Antardasha Yogini's ruling planet, informing the quality and harmony of each sub-period
Currently active Antardasha indicator — identification of whether any of the returned sub-periods is currently active at the time of the request, if the specified major Yogini period in the specified cycle is currently running
Cycle-specific Antardasha lookup — retrieving the Antardasha breakdown for a specific occurrence of a Yogini major period when the same Yogini appears in multiple cycles across the individual's lifetime and a particular cycle instance needs to be targeted precisely
Jyotish practitioners — accessing the sub-period structure of a specific Yogini period in a specific life cycle for client consultations, particularly when the individual is in their second or third Yogini Dasha cycle and the practitioner needs to distinguish between cycle occurrences
Astrology platforms and apps — powering Yogini Dasha drill-down features that allow users to select a specific Yogini period in a specific cycle and view its complete Antardasha sub-period breakdown
Future cycle planning — retrieving the Antardasha breakdown for a Yogini period in an upcoming cycle (e.g., cycle 2 or 3) to plan ahead for the sub-period structure of a future major Yogini period that has not yet begun
Historical cycle analysis — looking up the Antardasha breakdown for a Yogini period in a past cycle to correlate historical life events with the specific sub-periods that were active at the time
Comparative cycle analysis — comparing the Antardasha breakdowns of the same Yogini across different cycles to understand how the sub-period dates shift with each 36-year cycle repetition
Integration with event timing — combining the cycle-specific Antardasha dates with transit analysis or other timing tools to identify the most significant windows within a targeted Yogini sub-period
Accepts a dashaCycle path parameter (values: 1, 2, or 3) that specifies which repetition of the 36-year Yogini Dasha cycle to target — the critical differentiator from the Antar Yogini Dasha endpoint, which returns all cycles together, since the same Yogini recurs in each cycle with different calendar dates
Accepts a dashaKey path parameter specifying the major Yogini by name (mangala, pingala, dhanya, bhramari, bhadrika, ulka, siddha, or sankata), enabling direct targeting of any of the eight Yoginis within the specified cycle without requiring the caller to scan the full timeline
Computes all eight Antardasha sub-periods within the specified major Yogini period in a single response, providing the complete sub-period timeline for the targeted cycle instance
Calculates precise start and end dates for each Antardasha using the Yogini proportional formula anchored to the specific cycle instance's major period dates, ensuring the sub-period dates correctly reflect the targeted cycle rather than a generic calculation
Evaluates the inter-Yogini planetary relationship between the major Yogini's ruling planet and each Antardasha Yogini's ruling planet, providing the key interpretive data point for assessing sub-period quality
Preserves Yogini identity at both the major period and sub-period levels — each period is identified by Yogini name and associated planet, maintaining the Yogini system's distinct interpretive framework
Returns natal chart context for each Antardasha Yogini's associated planet — sign, house, dignity, and nakshatra — so the sub-period timeline is interpretively enriched
Accepts only birth details (date, time, and place of birth) with no current location required, since Yogini Dasha calculation is based entirely on the natal chart
Supports multiple Ayanamsha systems (e.g., Lahiri, Raman, KP) via the X-Ayanamsha header, since the Moon's nakshatra position — and therefore the entire Yogini Dasha timeline — varies by sidereal reference frame
Designed for localization — the Accept-Language header controls the language of Yogini names, planet names, nakshatra names, relationship labels, and all descriptive content in the response
Serves as the cycle-aware targeted complement to the Antar Yogini Dasha endpoint — use Antar Yogini Dasha for the full two-level timeline across all cycles, and this endpoint when a specific Yogini in a specific cycle needs to be targeted directly
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 Yogini Dasha By Cycle.
The Antar Yogini Dasha By Cycle API provides authentic Yogini 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 Yogini Dasha By Cycle 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 Yogini Dasha By Cycle consumes 1 API credit. The endpoint delivers high performance with an average response time of ~82ms.
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.