Public holidays, market closures and deadlines for 241 jurisdictions — every date carrying its evidence, its precision, and the day we last checked.
Engine — Edition — · how editions work
A moon-sighting holiday is not a fact until the decree. Most calendar sources return a confident date anyway. We return an estimate, say the announcement is pending, and name the authority it is pending from — so your code can decide whether that is good enough.
Which is also why there is a new edition every month. Governments revise dates, exchanges announce closures, ministries move deadlines, and religious authorities confirm observances only once they have been observed. The corpus is rebuilt monthly and every dossier reissued, with a page recording what moved since the last one. An edition is a position on a date, not a publication.
Questions that get expensive when they are answered badly.
Nine places where the date is the decision.
A regional holiday pays one state late.
Different closures. Confusing them moves money late.
Customs winds down before the holiday, not during.
Some jurisdictions roll forward, some back.
For software, the API. For a decision, a dossier. For planning, the Operating Calendar. Same evidence underneath; the difference is who has to read the answer.
For your systems
Your payroll, treasury or logistics software asks us directly, and gets back the date, what stands behind it, and how sure we are. Subdivisions inherit their national rules unless they override them.
For a decision
A dated briefing on one country: every closure, the evidence behind each one, and the CSV and calendar files to circulate. For the finance, legal and operations teams who need a document they can send round — not an endpoint, and not the same software.
For planning · in development
Put your markets on one calendar and see where they collide — which week is clear in all of them, whose office hours actually overlap, what your worst dates are. Free today for two places; the full tool is what we are building next.
No account, no card, no email. Each one shows its working — which day it excluded, what that day was called, and how well we can stand behind it.
Most calendars hand you a date. This one hands you the date, what stands behind it, and how sure we are.
A rule holds for years we have never published, and changes when the rule changes — not when someone remembers to update a spreadsheet.
Where a date is an estimate — a lunisolar rule awaiting a moon-sighting decree — we return it as an estimate rather than a confident wrong answer.
A bank holiday, a market closure, a tax deadline and a weather normal can fall on the same day, but they come from different authorities and move for different reasons. We keep them in separate layers and label each one, so a statistical estimate can never be read as a government gazette — and nothing we have not shipped is sold as though we had.