---
title: "Panchang Diwali"
method: GET
path: "/panchang/diwali"
---

# Panchang Diwali

`GET /panchang/diwali`

## 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/panchang/diwali`
- Auth: none declared

Gold-standard Diwali Lakshmi Puja muhurat for any location + year.

This is the FIRST gold-standard rule per the architecture brief.
Returns local civil date + exact Pradosh × Amavasya intersection
window + methodology fingerprint (diwali_lakshmi_puja_v1).

The 200 muhurat payload (window + methodology fingerprint + meta) is the
heaviest single-festival read-only SEO/AEO surface, so it is gzip-negotiated
via the audited `_json_response_maybe_gzip` helper: the DECOMPRESSED body is
byte-identical to the old `return _with_meta(result)` path (no
contract/field/value change), and the 404 (un-resolvable year) path is
unchanged. No PII; no reflected request input.

Example:
    GET /panchang/diwali?year=2025&lat=-33.8688&lng=151.2093&tz=Australia/Sydney

## Query parameters

- `year` integer, nullable
- `lat` number
- `lng` number
- `tz` string

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