Government
Public calendars that can withstand scrutiny
The problem
What is actually going wrong
Official holiday notifications and public event scheduling must be defensible. A date published by a department is expected to have a basis, and “the vendor’s software said so” is not one.
Our approach
Derive dates from versioned rules with named shastric authorities, and retain the trace so any published date can be reconstructed years later.
Workflow
How the integration runs
Derive
Generate the calendar for the relevant state or district.
Cross-check
Compare against that state’s own notified holiday list, which the API serves with the notification number, date and issuing authority.
Record
Store the rule id, version and trace alongside the notification.
Publish
Issue the calendar with its basis attached.
Reproduce
Any past notification can be regenerated exactly, on demand.
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
- Every published date reproducible from recorded rule versions
- Named authorities rather than an opaque calculation
- Regional variation handled through rule packs
- Civil closures cited to the notification that declared them, with amendments kept rather than overwritten
Build it this week
The Free plan covers 500 requests a month, which is more than enough to prototype the workflow above.