The Festivo Public Holidays API is still the fastest way to query official holidays by country, region, and city. Many teams also need a single governed definition of “which days count” for payroll, support rosters, or customer-facing schedules — without re-implementing merge rules in every service.
That is what holiday calendars in the workspace are for.
What you can do today
- Model — Create a named calendar, attach draft country + year sources, optional display renames, and preview the merged list before anyone depends on it.
- Override — Add blackout or extra working dates (with labels) so company closures and bridge days live in the same engine as public holidays.
- Publish — Immutable versions so downstream systems, exports, and widgets can pin to a snapshot. Compare two published versions when policies change.
- Compute — Call business-day operations (add, subtract, check, next working day, inclusive count between dates) and working-hours overlap against the calendar’s timezone and saved working window — or open the Business Time Lab in the portal to probe the same APIs interactively.
- Distribute — Authenticated ICS, public read-only pages when a calendar has a slug (with optional org-branded URLs), a compact month widget path for iframes, a small loader script on the portal host, and existing website widgets with scoped tokens and domain allowlists.
Where to read more
- Holiday calendars & website widgets — consolidated guide on getfestivo.com (paths, widgets, quotas).
- Create a free account — open Calendars after sign-in to try publish + exceptions end-to-end.
If you are only integrating the REST API today, you can keep using keys as before; calendars are there when you are ready to centralize how your org defines “a working day.”