Temple Management
Darshan schedules that follow the calendar, not a spreadsheet
The problem
What is actually going wrong
Temple timings shift with tithi, festival and muhurat. Most temple software encodes them as static opening hours, so every festival becomes a manual override — and the override is often applied a day late.
Our approach
Drive the schedule from the festival engine directly. Because each festival carries its derivation, an administrator disputing a date can be shown the rule and the authority rather than being asked to trust the software.
Workflow
How the integration runs
Subscribe
Register a webhook for festival events with a 7-day lead time.
Receive
An HMAC-signed event arrives ahead of each festival, carrying the date and confidence.
Adjust
Darshan slots and staffing are generated for the festival day automatically.
Justify
The explain trace is surfaced in the admin UI, so the committee can audit the date.
Integration
Endpoints and outcomes
Endpoints used
All of these are described in the OpenAPI 3.1 document, so you can generate a typed client rather than hand-writing request code.
What you get
- No manual festival calendar to maintain each year
- Disputes resolved with the rule and authority, not opinion
- Muhurat windows computed for the temple’s actual latitude
Build it this week
The Free plan covers 500 requests a day, which is more than enough to prototype the workflow above.