Real requests, against production
Nothing here is mocked. Every response below is fetched live from the same API your application would call, with no API key required.
GET /v1/panchang · /v1/festivals · /v1/muhuratconnecting…
Festival derivation
No festival on this date. The panchang below is still computed in full.
Intervals
—
Kala windows
No muhurat windows in this response.
Engine
The demo tier returns no cache headers, so cache state is not shown — we would rather omit the panel than display a value we cannot measure.
Try these
Dates worth looking at
8 November 2026
Diwali, decided at Pradosha
Amavasya covers the full 96-minute Pradosha window on the 8th and none of it on the 9th. Confidence 100. A sunrise-matching engine would pick the wrong day.
15 January 2027
Makar Sankranti
Decided by solar ingress rather than tithi. If the sun enters Makara after sunset, the observance shifts to the following day.
1 March 2026
An ordinary day
No major festival. Useful for seeing the plain panchang shape — tithi, nakshatra, yoga and karana with their interval boundaries.
What you are using
How the demo differs from the real API
The demo tier is fixed to New Delhi
location_id is honoured once you supply an API key. We would rather show you the parameter than pretend it is not there.Explainability depth
/v1/festivals/explain.Run it from your own code
The Code tab above gives you the exact request in curl and Python. Add a key and it works unchanged.
Where to next
Why is this date correct?
Methodology
Kala vyapini, the tie-break hierarchy, and how a date is decided.
ContinueHow do I integrate?
Developers
Quickstart, authentication, errors, webhooks and versioning.
ContinueCan I verify your claims?
Accuracy
Our verification tiers, our measurements, and what we still get wrong.
Continue