---
title: "Dasha Alerts Endpoint"
method: POST
path: "/alerts/dasha"
---

# Dasha Alerts Endpoint

`POST /alerts/dasha`

## Request

- Base URL: `https://jyotish-api.bda.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://jyotish-api.bda.ai/alerts/dasha`
- Auth: none declared

Subscription dasha-change alerts — the COMPUTE half of subscription
delivery/alerts. Builds the member's personal Jyotish bundle and returns every
Vimshottari Mahadasha / Antardasha / Pratyantardasha boundary that falls inside
the look-ahead `window_days`, i.e. the dates the running period's ruling planet
changes. Pure planetary-period arithmetic over the deterministic timeline the
bundle already carries — no astrological judgement, no fabrication.

Scheduled DELIVERY (recurring push / email on a cadence) is a separate
infrastructure layer that needs a worker + prod-config and is NOT performed here;
this endpoint computes the alert content on demand and discloses that in the
report's `delivery_note`. §12 guidance-not-fatalism; no scripture quoted.

## Request body

- DashaAlertsRequest
  - `name` string, nullable
  - `gender` string, nullable
  - `date_of_birth` string, date, required
  - `time_of_birth` string, required: HH:MM:SS in local time
  - `time_accuracy` string: exact|approximate|unknown
  - `lat` number, required
  - `lng` number, required
  - `tz` string, nullable
  - `window_days` integer: Look-ahead window in days to scan for upcoming dasha changes

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/bda/apis/bda-jyotish-panchang-service.md) · [All operations](https://skmtc.dev/bda/apis/bda-jyotish-panchang-service/llms.txt) · [OpenAPI document](https://skmtc.dev/bda/apis/bda-jyotish-panchang-service/revisions/90f241bf4009?raw)