Skip to main content
POST/v1/astro/dasha-transits

Dasha-Transit Correlation

Correlates active Vimshottari Dasha lords (maha, antar, pratyantar) with current planetary transits. Returns conjunction and aspect correlations scored by strength, and highlights periods of significance. Aspects are Vedic graha drishti cast by the transiting planet (BPHS Ch.26): every planet aspects its 7th sign, Jupiter also its 5th and 9th, Saturn its 3rd and 10th, Mars its 4th and 8th. Each correlation gives aspect_house (the natal dasha lord's sign counted from the transiting planet, 1 = same sign) and drishti ('7th', '3rd', ...; absent for a conjunction). aspect_type is conjunction, opposition, trine (Jupiter 5th/9th), square (Saturn 10th, Mars 4th) or special (Saturn 3rd, Mars 8th). Request JSON follows BirthInput plus optional target_date, target_time, target_timezone for the analysis moment: name, date, time, location or latitude/longitude/timezone, ayanamsa.

Request parameters​

locationoptional
string | null
City name to resolve to lat/lon/tz automatically. Example: 'Mumbai' or 'New Delhi, India'. If provided, latitude, longitude and timezone are not required.
nameoptional
string
Person name associated with the birth record
daterequired
string
Birth date in YYYY-MM-DD format
timerequired
string
Birth time in HH:MM 24-hour format. Required: this endpoint has no sunrise fallback.
latitudeoptional
number | null
Latitude. Required if location not provided.
longitudeoptional
number | null
Longitude. Required if location not provided.
timezoneoptional
string | null
IANA timezone. Required if location not provided (unless utc_offset is given). For dates before the zone adopted a standard time, the birthplace's local mean time (longitude / 15 hours) is used.
utc_offsetoptional
string | null
Optional explicit UTC offset of the birth time, as ±HH:MM or ±HH:MM:SS (e.g. '+04:51:31' for Bombay mean time). Overrides the offset timezone would give. Use it when the birth record states the offset, or for historical local times the IANA database cannot represent.
ayanamsaoptional
string
Sidereal ayanamsa mode used in calculations
target_dateoptional
string | null
YYYY-MM-DD. Defaults to today.
target_timeoptional
string | null
Local clock time HH:MM in target_timezone. Defaults to 12:00. Pass the user's own time so the Moon is where the user sees it.
target_timezoneoptional
string | null
Timezone for target date.

Response fields​

success
boolean
True if the request succeeded
message
string
Human-readable status message
data
object
data.birth_time_provided
boolean
True when a birth time was supplied. False when it was not: house, Ascendant and Moon-dependent results then carry the accuracy limits of an unknown birth time.
data.target_date
string
data.active_dasha
object
data.transit_positions
object
data.correlations
array[object]
Dasha lord × transiting planet aspects: dasha_level, dasha_lord, transit_planet, aspect_type (conjunction | opposition | trine | square | special), aspect_house (int 1-12: the natal dasha lord's sign counted from the transiting planet), drishti ('7th', '3rd', '10th', '5th', '9th', '4th', '8th'; absent for a conjunction), score, natal_rashi, transit_rashi, is_retrograde, significance. Aspects are cast by the transiting planet (BPHS Ch.26).
data.periods_of_significance
array[object]
Correlations with score ≥ 2, same shape as correlations.

Errors​

Invalid API key format.
API key is missing. Include it in the Authorization header as 'Bearer YOUR_KEY'.
The provided API key was not found. Verify the key in your Asterwise dashboard.
This API key has been revoked.
Too many requests per minute. Please slow down.
Something went wrong on our end. Please try again, or contact [email protected] if the problem persists. Include your request_id when contacting support.
Too many requests from this IP address. Please slow down.
Monthly API call limit reached. Upgrade your plan to continue.
Request body exceeds maximum allowed size of 64KB.
Your subscription has expired. Please renew at asterwise.com/dashboard to continue.
The request couldn't be processed. See the 'details' field for specific field-level issues.