API Reference / Vedic Astrology / Dasha
/v1/dasha/vimshottari/current
Current MD/AD/PD/SD/PPD period.
What this tells you
Returns the running Vimshottari period at all 5 levels for one moment: Maha, Antar, Pratyantar, Sookshma and Prana, each with its start and end. It is much smaller than the full tree from /v1/dasha/vimshottari. Use it for "you are here" displays and daily horoscope widgets.
Request
All requests require an Authorization header with your dv_live_* API key.
curl "https://api.lifeastroapi.com/v1/dasha/vimshottari/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": "vimshottari",
"at_jd": 2461420.5,
"at_local": "2027-01-15 05:30:00",
"maha": {
"lord": "Rahu",
"start_jd": 2459890.219622,
"end_jd": 2466464.719622,
"start_local": "2022-11-06 22:46:15",
"end_local": "2040-11-06 10:46:15"
},
"antar": {
"lord": "Jupiter",
"start_jd": 2460876.394622,
"end_jd": 2461752.994622,
"start_local": "2025-07-20 02:58:15",
"end_local": "2027-12-13 17:22:15"
},
"pratyantar": {
"lord": "Venus",
"start_jd": 2461307.389622,
"end_jd": 2461453.489622,
"start_local": "2026-09-24 02:51:03",
"end_local": "2027-02-17 05:15:03"
},
"sookshma": {
"lord": "Saturn",
"start_jd": 2461401.137122,
"end_jd": 2461424.269622,
"start_local": "2026-12-26 20:47:27",
"end_local": "2027-01-18 23:58:15"
},
"prana": {
"lord": "Rahu",
"start_jd": 2461417.715414,
"end_jd": 2461421.185289,
"start_local": "2027-01-12 10:40:12",
"end_local": "2027-01-15 21:56:49"
}
}Interactive preview
click any node to expandLevels: Mahadasha → Antardasha → Pratyantar → Sookshma → Praana. Built from the example response above, so each list shows its first two periods.
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 "vimshottari". example: "vimshottari" |
| 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 Maha Dasha at the query moment. example: { lord, start_jd, end_jd, start_local, end_local } |
| maha.lord | string | Ruling planet of the running Maha Dasha. example: "Rahu" |
| maha.start_jd, maha.end_jd | number | Period bounds as Julian Days (UT). example: 2459890.219622, 2466464.719622 |
| maha.start_local, maha.end_local | string | Period bounds as local time, same format as at_local. example: "2022-11-06 22:46:15", "2040-11-06 10:46:15" |
| antar | object | Running Antar Dasha (level 2). Same fields as maha. example: { "lord": "Jupiter", … } |
| pratyantar | object | Running Pratyantar Dasha (level 3). Same fields as maha. example: { "lord": "Venus", … } |
| sookshma | object | Running Sookshma Dasha (level 4). Same fields as maha. example: { "lord": "Venus", … } |
| prana | object | Running Prana Dasha (level 5). Same fields as maha. example: { "lord": "Saturn", … } |
Usage tips
How to use it
- Daily widgetThis is the endpoint for "what is my current dasha?" widgets. It costs 10 credits.
- Cache until the next changeThe answer changes when the shortest running period ends. Cache it no longer than prana.end_jd — a Prana period can be as short as about 20 minutes.
- Past or future datesPass `at` (for example at=2030-01-01) to see which periods run on that date.
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.