SEARCH ASTRO INSIGHT API DOCS
The Current Yogini Dasha 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/current-dasha
en
hi
ma
Methodology and astrological context for Current Yogini Dasha.
Returns the complete active Yogini Dasha state for a given natal chart at the current moment — a real-time convenience endpoint that resolves both levels of the Yogini Dasha hierarchy simultaneously and returns only the periods that are presently running, without requiring the caller to navigate the full timeline. This endpoint provides an immediate snapshot of the active major Yogini Dasha and its active Antardasha sub-period in a single call, serving as the most practical entry point for real-time Yogini Dasha analysis.
This endpoint accepts an individual's birth details and computes the currently active Yogini Dasha period at both the major period and Antardasha levels as of the moment the request is made. It identifies the active major Yogini (and which cycle repetition of the 36-year cycle it belongs to), the active Antardasha Yogini within that major period, and evaluates the natal chart condition of both active Yogini lords. The response also includes the inter-Yogini planetary relationship between the active major and sub-period lords, the time remaining in each active period, and the identity of the next Yogini transitions at both levels — providing a complete, immediately actionable real-time Yogini Dasha reference in a single response.
The response provides the full active Yogini Dasha state as of the time of the request:
Active major Yogini Dasha — the currently running major Yogini period, including the Yogini name, associated ruling planet, cycle number, and the major period's start and end dates
Active Antardasha — the currently running sub-period within the active major Yogini Dasha, including the sub-Yogini name, associated ruling planet, and the Antardasha's start and end dates
Associated planet natal positions — the zodiac sign, degree, house placement, nakshatra, and dignity of the ruling planets associated with both the active major Yogini and the active Antardasha Yogini in the natal chart
Inter-Yogini relationship assessment — an evaluation of the planetary relationship between the active major Yogini's ruling planet and the active Antardasha Yogini's ruling planet, indicating whether the current two-level combination is harmonious, conflicting, or neutral
Period remaining — the time remaining in both the active major Yogini period and the active Antardasha sub-period as of the current moment, giving an immediate sense of how far into each period the individual currently is and when the next transitions will occur
Upcoming transitions — the identity of the next Yogini at both the major period and Antardasha levels, along with the dates of the upcoming transitions, enabling forward-looking awareness of imminent period changes
Cycle reference — the cycle number of the currently active major Yogini period within the individual's lifetime, indicating whether the individual is in their first, second, or third repetition of the 36-year Yogini cycle
Nakshatra reference — the natal Moon's nakshatra and balance at birth, which anchors the entire Yogini Dasha timeline
Instant Yogini Dasha snapshot — retrieving the complete active Yogini Dasha state at both levels in a single call, without needing to first fetch the full major period timeline and then identify the active Antardasha
Jyotish practitioners — quickly establishing the current Yogini Dasha context at the start of a client consultation, providing the active major Yogini and Antardasha as an immediate reference alongside the Vimshottari Dasha state
Astrology platforms and apps — powering real-time Yogini Dasha dashboard widgets or home screen summaries that display a user's current Yogini period and sub-period at a glance, updated on each session
Cross-system real-time analysis — combining the current Yogini Dasha state with the current Vimshottari Dasha state to identify periods where both systems are simultaneously highlighting the same planetary influence, increasing prediction confidence
Transition alert systems — using the period remaining and upcoming transition data to trigger notifications when a user is approaching a Yogini Dasha transition at either the major period or Antardasha level
Onboarding and orientation — serving as the first Yogini Dasha call for new users of an astrology platform, giving them an immediate picture of their current Yogini period context before they explore the full timeline
Automated report generation — providing the current Yogini Dasha state as a structured data input for automated natal report generation pipelines that need the active Yogini period context without navigating the full hierarchy
Resolves the complete two-level active Yogini Dasha state — major Yogini period and Antardasha — in a single request, eliminating the need for sequential calls to establish the current Yogini context
Returns only the currently active periods at both levels rather than full sequences, making the response compact, immediately actionable, and directly interpretable without filtering
Includes period remaining at both levels as of the current moment, providing transition timing data that is immediately useful for practitioners and end users without requiring manual date arithmetic
Returns upcoming transition information at both levels — the next Yogini and transition date for both the major period and Antardasha — enabling forward-looking awareness of imminent period changes in a single response
Identifies the cycle number of the active major Yogini period, disambiguating which repetition of the 36-year cycle the individual is currently in — essential context for individuals in their second or third Yogini cycle
Evaluates the inter-Yogini planetary relationship between the active major and sub-period lords, providing the key interpretive data point for assessing the current two-level Yogini combination's overall quality
Returns natal chart context for both active Yogini lords — sign, house, dignity, and nakshatra — so the current snapshot is fully interpretively enriched rather than being a bare list of Yogini names and dates
Accepts only birth details (date, time, and place of birth) with no path parameters or current location required — the server determines the current moment automatically, keeping the request payload minimal
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 real-time entry point into the Yogini Dasha endpoint suite, complementing the full timeline endpoints (Major Yogini Dasha, Antar Yogini Dasha, Antar Yogini Dasha By Cycle) by providing an immediate current-state snapshot rather than a navigable timeline
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 Current Yogini Dasha.
The Current Yogini Dasha 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 Current Yogini 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 Current Yogini Dasha consumes 1 API credit. The endpoint delivers high performance with an average response time of ~31ms.
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.