POST · VEDIC

Ekadashi Dates

Endpoint POST https://starsapi.com/api/v3/vedic/panchang/ekadashi

Returns the month's Ekadashi calendar with full vrat logic: separate Smarta and Vaishnava observance dates (split entries when they differ), Suddha/Viddha tithi analysis, Mahadvadashi detection (Unmilani, Vyanjuli, Trisprisha, Paksha-Vardhini and others — cases where the fast moves to Dwadashi), adhik-masa Ekadashis (Parama / Padmini), and per-tradition parana windows with Hari Vasara end times. The year-wide summary and the next upcoming Ekadashi ride along with every call.

Dates are location-dependent — sunrise at the supplied coordinates decides the observance day, so the same Ekadashi can fall a day apart between cities.

Authentication

MethodExample
Header (recommended)X-Api-Key: am_live_xxxxxxxxxxxx
BearerAuthorization: Bearer am_live_xxxxxxxxxxxx
Query?api_key=am_live_xxxxxxxxxxxx

Request body

FieldTypeRequiredDescription
yearintegerYesCalendar year.
monthintegerYesMonth, 1–12 — the list is filtered to this month; summary and next still consider the whole year.
latitudenumberYesDecimal degrees.
longitudenumberYesDecimal degrees.
timezonestringYesIANA timezone (e.g. Asia/Kolkata).

Response shape

FieldTypeDescription
summaryobjectYear totals: entries, mahadvadashi count, adhik-masa months.
nextobjectThe next upcoming Ekadashi from today (full entry shape).
ekadashis[]arrayPer entry: observance date, tradition (smarta / vaishnava), name + Hindi, paksha, Hindu month in both systems, is_adhik, type (ekadashi / mahadvadashi with kind + description), tithi window (start, end, dwadashi end, Suddha flag), and parana per tradition (date, window, Hari Vasara end, notes).

Errors

HTTPCodeCause
400MISSING_FIELDRequired field absent.
400INVALID_DATEBad year/month.
400INVALID_TIMEZONENon-IANA timezone.
400INVALID_COORDINATELat/lon out of range.
405METHOD_NOT_ALLOWEDNon-POST request.

See also