Vimshottari Dasha API
Dasha Calculator API
Calculate current Vimshottari Dasha periods (Mahadasha, Antardasha, Pratyantardasha) with remaining time. Accurate dasha calculator API for life phase prediction and planetary period analysis. Returns dasha timeline with start/end dates for each period. Essential for understanding current planetary influences, dasha transitions, and timing events in Vedic astrology. 120-year dasha system based on moon nakshatra at birth.
Location first, chart second
The Vimshottari Dasha API needs latitude, longitude, and timezone. Never ask users to type coordinates. Resolve a city with the Location endpoint first, then feed the result into the request. Timezone accepts a decimal offset or an IANA name.
1 Resolve the location
curl "https://roxyapi.com/api/v2/location/search?q=New York" \
-H "X-API-Key: YOUR_KEY"
# -> cities[0]: { latitude, longitude, timezone: "America/New_York" }2 Call the Vimshottari Dasha endpoint
# feed latitude, longitude and timezone from step 1
POST https://roxyapi.com/api/v2/vedic-astrology/dasha/currentRequest
POST /api/v2/vedic-astrology/dasha/current
Parameters
| Parameter | Type | Description |
|---|---|---|
| langquery | string enum | Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. Default en. |
Request body
| Field | Type | Description |
|---|---|---|
| date* | string (date) | Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas). |
| time* | string (time) | Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect. |
| latitude* | number | Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172. |
| longitude* | number | Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240. |
| timezone | number or string | Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5. |
Example request
{
"date": "1990-07-04",
"time": "10:12:00",
"latitude": 28.6139,
"longitude": 77.209
}Response
Structured JSON with documented fields, verified against NASA JPL Horizons across 828 gold-standard tests. Not hallucinated text.
{
"moonNakshatra": 15,
"nakshatraName": "Swati",
"nakshatraLord": "Rahu",
"mahadasha": {
"planet": "Jupiter",
"startDate": "1990-07-04T10:12:00",
"endDate": "1996-07-04T10:12:00",
"durationYears": 6
},
"antardasha": {
"planet": "Jupiter",
"startDate": "1990-07-04T10:12:00",
"endDate": "1996-07-04T10:12:00",
"durationYears": 6,
"mahadashaLord": "Jupiter"
},
"pratyantardasha": {
"planet": "Jupiter",
"startDate": "1990-07-04T10:12:00",
"endDate": "1996-07-04T10:12:00",
"durationYears": 6,
"mahadashaLord": "Jupiter",
"antardashaLord": "Saturn"
},
"remainingInMahadasha": {
"years": 2,
"months": 4,
"days": 15,
"totalDays": 865
},
"remainingInAntardasha": {
"years": 2,
"months": 4,
"days": 15,
"totalDays": 865
},
"remainingInPratyantardasha": {
"years": 2,
"months": 4,
"days": 15,
"totalDays": 865
}
}Response fields
| Field | Type | Description |
|---|---|---|
| moonNakshatra* | integer | Birth Moon nakshatra number (1-27). This nakshatra determines the starting dasha lord in the Vimshottari 120-year cycle. |
| nakshatraName* | string | Name of the birth Moon nakshatra (lunar mansion). One of 27 Vedic nakshatras from Ashwini to Revati. |
| nakshatraLord* | string enum | Vimshottari dasha lord of the birth nakshatra. This planet rules the first Mahadasha in the native life cycle. |
| mahadasha* | object | Mahadasha (major planetary period) in the 120-year Vimshottari dasha cycle. Start and end dates are determined by Moon nakshatra at birth. |
| mahadasha.planet* | string enum | Ruling graha of this Vimshottari dasha period. One of 9 planets in the Ketu-Venus-Sun-Moon-Mars-Rahu-Jupiter-Saturn-Mercury sequence. |
| mahadasha.startDate* | string | Start datetime of this dasha period. Adjusted to the requested timezone offset. |
| mahadasha.endDate* | string | End datetime of this dasha period. Adjusted to the requested timezone offset. |
| mahadasha.durationYears* | number | Duration of this dasha period in years. Mahadasha durations range from 6 years (Sun) to 20 years (Venus). |
| mahadasha.interpretation | string | Vedic interpretation of the planetary period describing themes, karmic lessons, and life areas affected by this graha. |
| antardasha* | object | Antardasha (bhukti), sub-period within a Mahadasha. Each Mahadasha contains 9 Antardashas proportional to the Vimshottari years of each planet. |
| antardasha.planet* | string enum | Ruling graha of this Vimshottari dasha period. One of 9 planets in the Ketu-Venus-Sun-Moon-Mars-Rahu-Jupiter-Saturn-Mercury sequence. |
| antardasha.startDate* | string | Start datetime of this dasha period. Adjusted to the requested timezone offset. |
| antardasha.endDate* | string | End datetime of this dasha period. Adjusted to the requested timezone offset. |
| antardasha.durationYears* | number | Duration of this dasha period in years. Mahadasha durations range from 6 years (Sun) to 20 years (Venus). |
Show all fieldsShow fewer fields
| Field | Type | Description |
|---|---|---|
| antardasha.interpretation | string | Vedic interpretation of the planetary period describing themes, karmic lessons, and life areas affected by this graha. |
| antardasha.mahadashaLord* | string enum | Parent Mahadasha lord under which this Antardasha sub-period runs. |
| pratyantardasha* | object | Pratyantardasha (sub-sub-period), the third level of the Vimshottari dasha hierarchy, Provides finer timing within each Antardasha for event prediction. |
| pratyantardasha.planet* | string enum | Ruling graha of this Vimshottari dasha period. One of 9 planets in the Ketu-Venus-Sun-Moon-Mars-Rahu-Jupiter-Saturn-Mercury sequence. |
| pratyantardasha.startDate* | string | Start datetime of this dasha period. Adjusted to the requested timezone offset. |
| pratyantardasha.endDate* | string | End datetime of this dasha period. Adjusted to the requested timezone offset. |
| pratyantardasha.durationYears* | number | Duration of this dasha period in years. Mahadasha durations range from 6 years (Sun) to 20 years (Venus). |
| pratyantardasha.interpretation | string | Vedic interpretation of the planetary period describing themes, karmic lessons, and life areas affected by this graha. |
| pratyantardasha.mahadashaLord* | string enum | Parent Mahadasha lord under which this Antardasha sub-period runs. |
| pratyantardasha.antardashaLord* | string enum | Parent Antardasha lord under which this Pratyantardasha runs. |
| remainingInMahadasha* | object | Time remaining in the currently running Mahadasha (major period). |
| remainingInMahadasha.years* | number | Full years remaining in this Vimshottari dasha period. |
| remainingInMahadasha.months* | number | Additional months remaining beyond full years. |
| remainingInMahadasha.days* | number | Additional days remaining beyond full months. |
| remainingInMahadasha.totalDays* | number | Total remaining days in this dasha period. Useful for progress calculations. |
| remainingInAntardasha* | object | Time remaining in the currently running Antardasha (sub-period) within the Mahadasha. |
| remainingInAntardasha.years* | number | Full years remaining in this Vimshottari dasha period. |
| remainingInAntardasha.months* | number | Additional months remaining beyond full years. |
| remainingInAntardasha.days* | number | Additional days remaining beyond full months. |
| remainingInAntardasha.totalDays* | number | Total remaining days in this dasha period. Useful for progress calculations. |
| remainingInPratyantardasha* | object | Time remaining in the currently running Pratyantardasha (sub-sub-period). |
| remainingInPratyantardasha.years* | number | Full years remaining in this Vimshottari dasha period. |
| remainingInPratyantardasha.months* | number | Additional months remaining beyond full years. |
| remainingInPratyantardasha.days* | number | Additional days remaining beyond full months. |
| remainingInPratyantardasha.totalDays* | number | Total remaining days in this dasha period. Useful for progress calculations. |
Supported options
lang
Call it in your language in seconds.
Every snippet is generated from the live OpenAPI spec, so method names, parameters, and fields always match production.
import { createRoxy } from '@roxyapi/sdk'
const roxy = createRoxy(process.env.ROXY_API_KEY!)
const { data } = await roxy.vedicAstrology.getCurrentDasha({ body: { date: '1990-07-04', time: '10:12:00', latitude: 28.6139, longitude: 77.209 } })from roxy_sdk import create_roxy
roxy = create_roxy("YOUR_API_KEY")
result = roxy.vedic_astrology.get_current_dasha(date='1990-07-04', time='10:12:00', latitude=28.6139, longitude=77.209)use function RoxyAPI\Sdk\createRoxy;
$roxy = createRoxy(getenv('ROXY_API_KEY'));
$result = $roxy->vedicAstrology->getCurrentDasha(date: '1990-07-04', time: '10:12:00', latitude: 28.6139, longitude: 77.209);using RoxyApi;
var roxy = new RoxyClient(Environment.GetEnvironmentVariable("ROXY_API_KEY")!);
var result = await roxy.VedicAstrology.Dasha.Current.PostAsync(new() { /* request fields above */ });import roxyapi "github.com/RoxyAPI/sdk-go"
roxy, _ := roxyapi.NewRoxy(os.Getenv("ROXY_API_KEY"))
resp, _ := roxy.VedicAstrology.GetCurrentDasha(ctx, nil, roxyapi.GetCurrentDashaJSONRequestBody{ /* request fields above */ })curl -X POST "https://roxyapi.com/api/v2/vedic-astrology/dasha/current" \
-H "X-API-Key: YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"date":"1990-07-04","time":"10:12:00","latitude":28.6139,"longitude":77.209}'Prefer to try before you write code? Run this Vedic Astrology endpoint live in the API playground and inspect a real production response.
More Vimshottari Dasha endpoints
The Vimshottari Dasha API bundles these related endpoints under one key.
Get all 9 Mahadasha periods (120-year cycle)
Returns complete Vimshottari Dasha cycle starting from birth. Shows all major planetary periods from birth through 120 years.
Try it liveGet all Antardashas (sub-periods) for a specific Mahadasha
Returns 9 Antardasha sub-periods within a Mahadasha. Each Mahadasha is divided into 9 proportional sub-periods.
Try it liveRemote MCP for AI agents
Every Vedic Astrology endpoint is a callable tool on the Remote MCP server over Streamable HTTP. No local setup, no Docker. Claude, ChatGPT, Cursor, and any MCP client auto-discover the tools and ground their answers in verified data.
claude mcp add --transport http \
roxy-vedic-astrology https://roxyapi.com/mcp/vedic-astrology \
--header "X-API-Key: YOUR_KEY"Tool name for POST /vedic-astrology/dasha/current: post_vedic_astrology_dasha_current. Full MCP setup guide
What you can build
Matrimonial matchmaking platforms - automate Gun Milan compatibility scoring, Manglik dosha checks, Navamsa spouse analysis, and generate match reports with remedies for Shaadi.com-style features
Daily horoscope and prediction apps - fetch planetary transits, current Dasha periods, Panchang data, and birth star forecasts to power personalized daily readings at consumer-app scale
Kundli generation and PDF report services - combine D1/D9 charts, planetary positions, Dasha timelines, yoga detection, and dosha analysis into automated birth chart reports
KP horary and event prediction apps - build stellar astrology software with significator analysis, cusp sub-lords, and 249-level precision for answering when/yes-no questions
Spiritual wellness and calendar apps - integrate Panchang for Hindu festival dates, fasting calendars, temple muhurat selection, and Nakshatra-based meditation schedules
AI astrology chatbots and virtual consultants - power conversational AI with structured Vedic calculations, compatibility queries, Dasha predictions, and remedy suggestions via ChatGPT plugins or MCP integration
Drop-in UI components
Render Vimshottari Dasha API responses without building charts yourself. These open source, framework-agnostic web components take the typed response and draw it, in React, Vue, Svelte, Angular, plain HTML, and WordPress.
Related capabilities
Vimshottari Dasha API FAQ
What does the Vimshottari Dasha API return?
Calculate current Vimshottari Dasha periods (Mahadasha, Antardasha, Pratyantardasha) with remaining time. Every response is structured JSON with documented fields, not free text, so you map it straight into your product.
How do I authenticate with the Vimshottari Dasha API?
Pass your key in the X-API-Key header on every request. Keys are delivered instantly at checkout with no approval queue. Use a secret sk key server side, or mint a publishable pk key locked to your origins for browser and no-code use.
Does the Vimshottari Dasha API support multiple languages?
Yes. Append the lang query parameter to any endpoint for responses in English, German, Spanish, French, Hindi, Portuguese, Russian and Turkish. The translated payload includes the full interpretation text, not just field labels.
Do I need coordinates to call the Vimshottari Dasha API?
No. Call GET /location/search with a city name first, then pass latitude, longitude, and timezone from the first result into the request. Never ask users to type coordinates. Timezone accepts a decimal offset or an IANA name.
Is the Vimshottari Dasha API available over Remote MCP for AI agents?
Yes. Every endpoint is exposed as a callable tool on the Remote MCP server at https://roxyapi.com/mcp/vedic-astrology over Streamable HTTP, so Claude, ChatGPT, Cursor, and any MCP client auto-discover it with no local setup or Docker.
How is the Vimshottari Dasha API billed?
Flat pricing: 1 request equals 1 quota unit, REST and MCP identical, with no credit weighting or per-token markup. Every plan includes all 12 domains, so the Vimshottari Dasha API is included at no extra cost.
What lang values does the Vimshottari Dasha API accept?
The lang parameter accepts en, tr, de, es, hi, pt, fr, ru. Case-insensitive where it is a path value.
Start using Vimshottari Dasha API today.
Launch your Jyotish or KP astrology product in days. Not months.
All 12 domains included with every plan. Every endpoint, MCP server, SDK, and starters.
Plans from $39/mo, starting at $2.70 per domain on annual billing. No credit card required for testing.
View Pricing & Get API Key