API Reference / Vedic Astrology / Dasha
/v1/dasha/yogini/current
Current Yogini period.
What this tells you
Returns the running Yogini Maha Dasha and Antar Dasha at one moment — the Yogini version of /v1/dasha/vimshottari/current. Yogini Dasha repeats every 36 years, so any moment after the start of the first cycle works. The dates returned belong to the cycle the moment actually falls in.
Request
All requests require an Authorization header with your dv_live_* API key.
curl "https://api.lifeastroapi.com/v1/dasha/yogini/current?date=1990-01-15&tz=Asia%2FKolkata&lat=19.076&lon=72.8777&time=10%3A30&at=2027-01-15T00%3A00%3A00Z" \
-H "Authorization: Bearer YOUR_API_KEY"Query parameters
Checked against the API: a parameter is marked required when the request fails without it.
| Name | Required | Example | Description |
|---|---|---|---|
date | yes | 1990-01-15 | Birth date (YYYY-MM-DD). |
tz | yes | Asia/Kolkata | Birth place timezone: IANA name (Asia/Kolkata) or UTC offset (+05:30). |
lat | yes | 19.076 | Birth place latitude in decimal degrees. |
lon | yes | 72.8777 | Birth place longitude in decimal degrees. |
time | no | 10:30 | Birth time (HH:MM, 24-hour, local). Defaults to 12:00. |
at | no | 2027-01-15T00:00:00Z | UTC moment to find the running dasha for (RFC3339 like 2027-01-15T00:00:00Z, or YYYY-MM-DD). Defaults to now. |
ayanamsa | no | — | Ayanamsa (sidereal offset) to use. Defaults to lahiri. |
Response (200 OK)
The real response to the example request above, generated from the API itself. Long arrays are trimmed to their first two items. Field names are stable across versions.
{
"birth_date": "1990-01-15",
"birth_time": "10:30",
"location": {
"lat": 19.076,
"lon": 72.8777,
"alt": 0
},
"tz": "Asia/Kolkata",
"ayanamsa": "lahiri",
"ayanamsa_value": 23.71795,
"system": "yogini",
"at_jd": 2461420.5,
"at_local": "2027-01-15 05:30:00",
"maha": {
"lord": "Ulka",
"planet": "Saturn",
"start_jd": 2459939.03672,
"end_jd": 2462130.53672,
"start_local": "2022-12-25 18:22:53",
"end_local": "2028-12-25 06:22:53"
},
"antar": {
"lord": "Dhanya",
"planet": "Jupiter",
"start_jd": 2461400.03672,
"end_jd": 2461582.66172,
"start_local": "2026-12-25 18:22:53",
"end_local": "2027-06-26 09:22:53"
}
}Field reference
Every field in the response, with its type, a real example, and what it means.
| Field | Type | Meaning |
|---|---|---|
| birth_date, birth_time | string | Birth date and time, echoed from `date` and `time`. example: "1990-01-15", "10:30" |
| location | object | Birth place, echoed from `lat`, `lon` and `alt`. example: { "lat": 19.076, "lon": 72.8777, "alt": 0 } |
| tz | string | Birth timezone. Its UTC offset at birth is used for every `*_local` string. example: "Asia/Kolkata" |
| ayanamsa, ayanamsa_value | string, number | Ayanamsa name and its value in degrees at birth. example: "lahiri", 23.71795 |
| system | string | Always "yogini". example: "yogini" |
| at_jd | number | The query moment as a Julian Day (UT). Comes from `at`; defaults to the time of the request. example: 2461420.5 |
| at_local | string | The query moment as local time ("YYYY-MM-DD HH:MM:SS"), using the birth UTC offset. example: "2027-01-15 05:30:00" |
| maha | object | Running Yogini Maha Dasha. example: { lord, planet, start_jd, end_jd, start_local, end_local } |
| maha.lord | string | Running Yogini name. example: "Ulka" |
| maha.planet | string | Ruling planet of that Yogini. example: "Saturn" |
| maha.start_jd, maha.end_jd | number | Period bounds as Julian Days (UT), in the cycle the query moment falls in. example: 2459939.03672, 2462130.53672 |
| maha.start_local, maha.end_local | string | Period bounds as local time, same format as at_local. example: "2022-12-25 18:22:53", "2028-12-25 06:22:53" |
| antar | object | Running Antar Dasha inside the Maha Dasha. Same fields as maha. example: { "lord": "Pingala", "planet": "Sun", … } |
Usage tips
How to use it
- Pair with Vimshottari currentShow the Vimshottari and Yogini "you are here" results side by side in dashboards.
- Cache until antar.end_jdThe result only changes when the running Antar Dasha ends, so it can be cached until antar.end_jd.
Errors
Every error follows the same envelope. Use the error.code field (not the message) for conditional logic in your integration.
401 Unauthorized
{
"error": {
"code": "unauthorized",
"message": "missing or invalid API key",
"request_id": "req_01hqy7k8c3e7m1n"
}
}402 Payment Required
{
"error": {
"code": "trial_exhausted",
"message": "your free trial credits are exhausted — pick a plan to continue",
"top_up_url": "https://lifeastroapi.com/pricing",
"request_id": "req_01hqy7k8c3e7m1n"
}
}429 Too Many Requests
{
"error": {
"code": "rate_limited",
"message": "rate limit exceeded; retry after 12 seconds",
"request_id": "req_01hqy7k8c3e7m1n"
}
}Try it
Get a dv_live_* key from your dashboard and paste into the cURL snippet above. New accounts get 1,500 free credits. Sign up.