curl -X POST https://yogataraapi.prahlad.app/api/astro/muddha_dasha/ \
-H "X-API-Key: $OCCULT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"keys":["mudda_dhasa_bhukthi"],"years":0,"date_time":"2025-02-13T05:10:10.565Z","include_antardhasa":true,"latitude":26.9124,"longitude":75.7873,"timezone_as_float":5.5}'Muddha dasha, also called Varsha Vimshottari, is the annual-chart counterpart of the ordinary Vimshottari dasha: the same nine planetary periods in the same sequence, compressed from 120 years into the single solar-return year you are examining. It is one of the standard timing tools of Tajika (Varshaphala) practice, used to say which stretch of a particular year belongs to which planet. Pass the birth details plus years — the number of completed years since birth, which selects the annual chart — and include_antardhasa. With antardashas you get 81 rows; without, nine. Two things to watch in the output. The lords are integers rather than names: 0 Sun, 1 Moon, 2 Mars, 3 Mercury, 4 Jupiter, 5 Venus, 6 Saturn, 7 Rahu, 8 Ketu. And each start date is a string of the form "2025-02-02 {'degrees': 13, 'minutes': 0, 'seconds': 54.16}", where the braced part is the time of day left in the degrees-minutes-seconds form the Julian-day conversion produced rather than converted to hours. Durations are in days, and the nine top-level periods add up to one tropical year.
| Field | Type | Required | Notes |
|---|---|---|---|
| date_time | string (date-time) | required | The moment to calculate for, ISO 8601. ALWAYS include an offset or a trailing Z - a value with no zone is read as Asia/Kolkata (UTC+05:30), not UTC, and can return the previous day's result with a 200. '2026-09-01T06:00:00Z' and '2026-09-01 06:00:00' are different instants and give different answers. |
| include_antardhasa | boolean | required | |
| keys | array | required | Which calculations to return, as a list of names. See the key table for this endpoint; an unrecognised name rejects the whole request. One call costs one credit however many keys you ask for, so request everything you need at once rather than making several calls. |
| latitude | number (double) | required | Latitude of the place, in decimal degrees. Positive is north, negative is south. Example: 26.9124 for Jaipur, 40.7128 for New York. Minutes and seconds are not accepted - convert first. min -90 · max 90 |
| longitude | number (double) | required | Longitude of the place, in decimal degrees. Positive is east, negative is west. Example: 75.7873 for Jaipur, -74.0060 for New York. Note the sign: a missing minus puts New York in China. min -180 · max 180 |
| timezone_as_float | number (double) | required | UTC offset of the place, in hours, as a decimal. Example: 5.5 for India (UTC+05:30), -5 for New York in winter, 5.75 for Nepal. This is NOT validated against date_time - if the two disagree you get a successful response for the wrong moment, so derive both from the same source. Use the offset in force on that date, not today's: a summer birth in a country with daylight saving needs the summer offset. min -12 · max 14 |
| years | integer | required |
Ask for exactly the calculations you want by listing them in keys. An unknown key rejects the whole request, and you are charged 1 credit however many you ask for — so batch them.
| Key | Extra fields needed | Description | |
|---|---|---|---|
| mudda_dhasa_bhukthi | include_antardhasa | The Muddha (Varsha Vimshottari) periods for the annual chart selected by years. With include_antardhasa true it returns 81 rows of [dasha lord, bhukti lord, start, duration]; with it false, nine rows of [dasha lord, start, duration]. Lords are integers (0 Sun, 1 Moon, 2 Mars, 3 Mercury, 4 Jupiter, 5 Venus, 6 Saturn, 7 Rahu, 8 Ketu), durations are in days summing to one tropical year, and each start is a string combining the date with a degrees-minutes-seconds rendering of the time of day. |