---
title: "Muhurat Electional Endpoint"
method: POST
path: "/muhurat/electional"
---

# Muhurat Electional Endpoint

`POST /muhurat/electional`

## 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/muhurat/electional`
- Auth: none declared

Electional Muhurat — rank auspicious time windows across a date range from
the universal classical Panchang signals (Choghadiya class + Abhijit, minus
the Rahu/Yamaganda/Gulika malefic windows). Deterministic: per-day core-
Astronomical core Panchang in, ranked windows out; the LLM only narrates.

Activity-specific muhurat selection is pandit-gated and NOT asserted here — an
`activity` is echoed back flagged `pending_pandit_ratification` (§8.3).

## Request body

- ElectionalMuhuratRequest
  - `lat` number, required
  - `lng` number, required
  - `start_date` string, date, required: First local date to scan (YYYY-MM-DD)
  - `days` integer: Number of days to scan from start_date
  - `tz` string, nullable: IANA timezone (auto-resolved from lat/lng if omitted)
  - `activity` string, nullable: Optional activity (e.g. griha_pravesh, vivah). Echoed only — activity-specific muhurat rulesets are pandit-pending; the ranking is activity-agnostic universal classical signals.
  - `top_n` integer: How many top windows to return
  - `profile` string: Regional profile

## 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)