Overview
A Kundli describes the chart at a single moment. Dashas and doshas add two further dimensions: time and chart conditions. Both are derived from the same birth input used everywhere in the Horoscope guides — Aarav Sharma, born 1990-08-15 at 10:30 in Kolkata.
Use this to understand the shape of dasha and dosha responses. See Documentation for the complete field schema and error codes.
The Dasha Endpoint
Vimshottari dasha divides a life into planetary periods (mahadashas) and sub-periods (antardashas). The dasha endpoint returns this sequence with the ruling planet and the start and end of each period, so your product can highlight the current period and show what comes next.
Call it with the standard birth input:
curl -X POST https://horoscope.devdarsha.com/v1/dasha \
-H "content-type: application/json" \
-H "x-api-key: YOUR_API_KEY" \
-d '{"date":"1990-08-15","time":"10:30","city":"Kolkata"}'To show a “current period” banner, find the period whose start and end span today’s date, and read its ruling planet.
The Dosha Endpoint
The dosha endpoint reports whether specific chart conditions are present. Each result is a flag with supporting detail, so your UI can show the condition and the factors behind it rather than a bare yes or no. Treat every flag as descriptive chart information for the user to interpret, and keep the copy around it neutral.
How to Use These in a Product
A common pattern is a birth-profile screen that combines all three: the Kundli for the chart, the dasha for a timeline, and the dosha for chart notes. Load the Kundli first, then request dashas and doshas as the user drills in, so a profile renders quickly and heavier data loads on demand.
Present dashas and doshas as structured chart information. Let users read and interpret the data; keep surrounding copy factual and free of assurances.
Display Tips
Label periods with their ruling planet and date range. Group antardashas under their mahadasha so the hierarchy is clear. For doshas, show the contributing factors alongside each flag. Treat any field as optional so a plan-gated or missing value never breaks the screen.