Skip to main content
ClavisCore

DaysUnit

Zero-infrastructure, open calendar data for UEMOA member states β€” public holidays, working day flags, and payroll-critical dates served as static JSON from a global CDN, with a runtime-agnostic JavaScript library and CLI for offline caching.

[ABOUT]

About

DaysUnit provides per-day working day, public holiday, and calendar metadata for UEMOA member states as static JSON files, served from a global CDN at days.claviscore.com with no API keys, no rate limits, and no backend runtime required for reads. An accompanying TypeScript library (@claviscore/days) wraps the CDN with a fluent API supporting single-day lookups, month ranges, multi-country batch queries, and navigation helpers (nextWorkingDay, workingDaysInRange). A CLI ships with the package for pre-downloading data into a local offline cache, enabling zero-latency lookups in server-side applications. V1 covers BΓ©nin (BJ) with the full UEMOA zone on the immediate roadmap under the same schema and without breaking changes. Calendar data carries a confidence field (confirmed / tentative / ai-generated) and links each holiday record to its legal basis in the Journal Officiel. Dual-licensed: source code MIT, calendar data CC BY 4.0.

[FEATURES]

Key Features

Zero Infrastructure: Data served as static JSON from a CDN β€” no server runtime, no API keys, no rate limits, full CORS support for direct browser consumption
Rich Day Schema: 25 fields per day including isWorkingDay, isPublicHoliday, isFirstWorkingDayOfMonth, isLastWorkingDayOfMonth, isRamadanPeriod, legalBasis, source URL, and confidence rating
Runtime-Agnostic Library: @claviscore/days works in Browser, Node β‰₯ 18, Deno, and Bun; ships zero bundled calendar data β€” fetched from CDN or local cache at runtime
Offline CLI: npx @claviscore/days pull pre-downloads full country/year datasets into a local .days/ cache for zero-latency server-side lookups
Multi-Country Batch API: days(['BJ','CI','SN']).on('2026-01-01') issues parallel fetches and returns a typed result map across all requested countries
Confidence-Rated Data: Every record carries confirmed / tentative / ai-generated provenance with a source URL pointing to the official legal document
SYSCOHADA-Ready: isLastWorkingDayOfMonth and workingDayOfMonth fields directly support SYSCOHADA journal closing date computations and payroll cut-off logic
[USAGE]

Use Cases

  • Payroll systems requiring accurate UEMOA working-day and public holiday calendars
  • SYSCOHADA accounting software computing journal closing dates and payment deadlines
  • HR and leave management platforms enforcing country-specific non-working days
  • Scheduling and logistics applications operating across multiple UEMOA territories
  • SaaS products needing reliable, zero-maintenance calendar data with no backend dependency
[AUDIENCE]

Target Users

Fintech DevelopersERP/SaaS EngineersUEMOA Market BuildersBackend Teams