Catalogue breadth vs holiday depth
A multi-product marketplace is convenient when you want one vendor and many unrelated endpoints. It is less helpful when your risk is misaligned holiday definitions between your billing engine, your HR calendar, and your customer portal — that is a workflow and publishing problem, not only another REST call.
- Coverage posture: Festivo emphasises granular regions, city-level support where your plan allows, and broad translations — all documented alongside portal behaviour, not only a generic holidays stub.
- EU operations: Festivo is made and hosted in the EU with transparent B2B billing patterns (invoicing, tax identifiers, purchase orders on supported plans) aimed at teams that buy software deliberately.
When Abstract-style APIs are enough
If you only need an occasional holiday check inside a prototype, a bundled micro-API can be fine. When holidays become contractual — SLAs, customer comms, HR alignment — you will want immutable publish, audit-friendly HR adapters, and SSO-backed access to match how you run the rest of the stack.
A workspace on top of the same holiday data
Many vendors stop at “here is JSON for a country/year.” Festivo keeps that contract for engineers, then adds a control plane so product, HR, and operations can agree on what “a holiday” means for your organisation before it hits production code or customer-facing calendars.
Governed calendars, not ad-hoc spreadsheets
- Named calendars composed from authority sources, with draft → publish, immutable snapshots, and version compare for approvers.
- Blackouts and working-day exceptions layered on official data — carried through publish so APIs, widgets, and exports stay aligned.
- Per-calendar timezones and working-hours profiles so downstream consumers see holidays the way your business actually runs.
Public pages, ICS, and embeddable widgets
- First-party read-only calendar views (month, week, agenda) with stable URLs people can bookmark — not only machine-readable JSON.
- ICS exports and a hosted widget path with scoped publish tokens and origin controls where your plan allows embeds.
- Optional org-branded public paths so intranet and marketing surfaces sit under a namespace you recognise.
Business-time APIs tied to those calendars
Scheduling helpers (next working day, inclusive counts, overlap probes) run against the same published rules as your widgets — not a generic weekend skip disconnected from your blackout list.
An authenticated Business Time Lab lets engineers and PMs probe behaviour before wiring production services.
HR signals, SSO, and automation
- HiBob integration (Growth and above) to align company calendar and time-off signals with Festivo calendars, publish, ICS, and widgets — see HR integrations.
- Enterprise OIDC / SAML for how staff sign in to the workspace — see Enterprise SSO.
- Signed user webhooks with test delivery so Slack, Teams, or internal orchestration can react when publishes and related events happen — see Webhooks.
Portal built for B2B operations
- Playground with persisted requests, OpenAPI / Postman export, holidays explorer with watchlists and share links, and usage-aware analytics.
- Billing depth (cards, EU tax IDs, invoices, purchase orders on supported plans), notification centre, and clear quota / lifecycle banners.
- Help hub, structured support intake, public status, and documentation that covers both API and portal workflows.
Pricing · Calendars & widgets · Documentation · All comparisons