---
title: "Dasha-Transit Correlation"
method: POST
path: "/v1/astro/dasha-transits"
tags: ["Astrology"]
---

# Dasha-Transit Correlation

`POST /v1/astro/dasha-transits`

## Request

- Base URL: `https://api.asterwise.com`
- URL: `https://api.asterwise.com/v1/astro/dasha-transits`
- Auth: HTTP bearer

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 body

- DashaTransitsRequest: Dasha–transit correlation — extends :class:`TimedBirthInput`. Birth fields: ``name``, ``date``, ``time``, ``location`` or ``latitude``/``longitude``/ ``timezone``, ``ayanamsa``. Optional analysis instant: ``target_date``, ``target_time``, ``target_timezone``.
  - `location` string, nullable: City name to resolve to lat/lon/tz automatically. Example: 'Mumbai' or 'New Delhi, India'. If provided, latitude, longitude and timezone are not required.
  - `name` string: Person name associated with the birth record
  - `date` string, required: Birth date in YYYY-MM-DD format
  - `time` string, required: Birth time in HH:MM 24-hour format. Required: this endpoint has no sunrise fallback.
  - `latitude` number, nullable: Latitude. Required if location not provided.
  - `longitude` number, nullable: Longitude. Required if location not provided.
  - `timezone` string, nullable: 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_offset` string, nullable: 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.
  - `ayanamsa` 'lahiri' | 'raman' | 'kp' | 'tropical': Sidereal ayanamsa mode used in calculations
  - `target_date` string, nullable: YYYY-MM-DD. Defaults to today.
  - `target_time` string, nullable: 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_timezone` string, nullable: Timezone for target date.

## Response `200`

Successful Response

- ApiResponseDashaTransitsResponse
  - `success` boolean: True if the request succeeded
  - `message` string: Human-readable status message
  - `data` DashaTransitsResponse, required
    - `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.
    - `target_date` string, required
    - `active_dasha` object, required
    - `transit_positions` object, required
    - `correlations` object[], required: 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).
    - `periods_of_significance` object[], required: Correlations with score ≥ 2, same shape as correlations.

## Other responses

- `401`: Authentication failed
- `403`: Authorization failed
- `404`: Resource not found
- `413`: Payload too large
- `422`: Validation error
- `429`: Rate limit exceeded
- `500`: Internal error
- `502`: Upstream provider error
- `503`: Service unavailable

---

[API](https://skmtc.dev/asterwise/apis/asterwise-api.md) · [All operations](https://skmtc.dev/asterwise/apis/asterwise-api/llms.txt) · [OpenAPI document](https://skmtc.dev/asterwise/apis/asterwise-api/revisions/3c4bbb1194e2?raw)