The Panchang API: the entire Hindu calendar, one endpoint.
Tithi, Nakshatra, Yoga, Karana, Vara, Ghaṭī, Muhurta, Kaal, Hora and Choghadiya — astronomically computed for any coordinate and returned as one clean JSON payload. No scraping. No stitching. No ayanamsha mistakes.
Every Panchang app rebuilds the same hard parts. We did it once — correctly.
Panchang is not a calendar lookup. It is astronomy + conventions. One wrong ayanamsha, one wrong sunrise definition, one flat 24h ghati — and your Tithi, Muhurat and Kaal are off by hours.
DIY breaks at the edges
Chitra Paksha vs. Raman vs. KP, Amanta vs. Purnimanta, Drik vs. geometric sunrise, 60 equal ghati vs. proportional dinaman — pick wrong and festivals shift a day. Our metadata.conventions stamps exactly what was used.
Coordinate, not city
Pune sunrise ≠ Delhi sunrise. Dinaman, ghati, and Nakshatra kaal are computed for your lat/lon/elev/tz, not a city table. Works for New York to Sydney.
One payload, not five libraries
Swiss Ephemeris + time-windows + i18n names + paksha + pada + vara — one GET, one compute pass, no gluing astronomy, JSON, and Hindi transliteration together.
Everything a Panchang app needs, pre-computed.
Stop stitching. Start shipping. Every group below is live in the same response.
One payload, no stitching
GET /api/panchang returns panchanga + civil + astronomy + calendar + traditional_time + time_windows together — the exact dictionary teams keep rebuilding by hand.
Coordinate-accurate astronomy
True sunrise/sunset, dinamana/ratrimana in ghati, sidereal Sun/Moon, ayanamsha, elongation and Moon phase — per coordinate.
Muhurat & Kaal, derived
Rahu Kaal, Yamaganda, Gulika, Abhijit, Vijay, Brahma, Godhuli, Amrit Kaal, Varjyam, Bhadra flag, Dur Muhurtam — with method provenance.
Hora & Choghadiya, 24h
Planetary Hora rulers hour-by-hour + Choghadiya's 7-name cycle for day and night — ready to render.
Localized names, free
Every element in Devanagari ?lang=hi or IAST ?lang=en — no extra dictionary. Tithi प्रतिपदा, Nakshatra श्रवण, Vara शनि included.
Free key to start
Sign up, create a key, call from browser, server, or cron. CORS-enabled, JSON, no-cache live. Keyless demo (3/day) for instant tries.
How it works — request → ephemeris → Drik → you.
Swiss Ephemeris + Lahiri + Drik sunrise. Not a scraped PDF.
You request a place + instant
?lat=&lon=&tz=&instant=&lang=. No SDK. curl in the docs works from the browser.
curl "…/api/panchang?lat=18.52&lon=73.86&tz=Asia/Kolkata&lang=hi"
We compute — per second, per coordinate
Sidereal longitudes, ayanamsha, sunrise-set, ghati/muhurta/prahara, then derived windows (Rahu, Hora, Choghadiya). Same engine that drives /panchang-today.
You render — no parsing debt
One JSON shape forever. metadata.conventions + location let you audit. Cache by instant if you want.
Who ships with this?
Not an end-user astrology app. A primitive for teams who build them.
Muhurat finders
Abhijit, Amrit, Bhadra Vas, Hora — filter by time_windows and show the next good slot. No manual ghati math.
Calendar & temple widgets
Month view with Tithi + Paksha + Saka + Samvatsara. ?lang=hi gives you Devanagari for free.
Automation & content
Daily Panchang cron, festival alerts, print-ready sheets. One endpoint powers web, app, and PDF.
Build vs. buy — honestly.
We love libraries. This is where they cost you.
If you already have a tested Drik stack, keep it. If you are stitching, this saves the edge-case weeks.
Proven, not promised.
Same engine. Two surfaces: API and clock. Validated against the official Rāṣṭrīya Pañcāṅga 1948.
71/71 Rāṣṭrīya Pañcāṅga 1948
Against the official Drik almanac: 71 festival cases plus a 44-day audit of tithi, nakshatra, sunrise and end-times. Run the validator in the repo.
Sunrise-anchored, RP-validated
Drik-method sunrise with proportional dinaman/ratrimana — refraction-corrected RP-almanac mode via ?convention=rp_almanac. Ghaṭī is not 24m flat — it breathes with the day length for your coordinate.
Live reference: /panchang-today
The Indian Traditional Clock calls the same API and renders it. Same code path. No hidden logic.
Questions teams actually ask.
Is this Lahiri? Which sunrise?
Lahiri (Chitra Paksha) ayanamsha with Drik-method sunrise — geometric Hindu rising by default, refraction-corrected upper-limb via ?convention=rp_almanac (the RP-1948-validated mode). Stamped in every response — audit it.
Amanta vs Purnimanta?
We return Paksha + lunar Masa; apply your sampradaya. No hidden month flip.
What about festivals / yearly Panchang dump?
Shipped: /api/panchang carries calendar_events, fasting_tags and parana_metadata — plus GET /api/calendar/month for full-month grids. See the month calendar.
Can I cache?
Yes — vary on lat/lon/instant/tz/lang. Response is no-cache live but deterministic per instant.
Why Ghaṭī and not minutes?
We give you both: traditional_time (ghati/pala/vipala/muhurta/prahara) and IST for windows. Render which your user expects.
Speed?
One endpoint, one compute pass, no fan-out. Measure it yourself in the docs try-it console — you just fetch.
Build the clock. Or anything else.
The same engine powers our live Indian clock — and your next product. Star a repo, ship a widget, print a Panchang. All from one endpoint.