Non-Working Days API vs The Calendar API

Two free Calendar APIs compared on access, reliability and developer ratings, using data from our daily health checks.

The verdict

Choose Non-Working Days API if its data fits your use case better; on access and reliability it's level with The Calendar API.
Choose The Calendar API if you want faster responses.

	Non-Working Days API	The Calendar API
What it does	Simple REST API for checking working, non-working or short days for Russia, CIS, USA and other.	Public holidays for US states and 30 countries plus sports and finance calendars as static JSON.
Provider	isDayOff()	the-calendar.net
API key	Not needed	Not needed
HTTPS	Yes	Yes
CORS (browser calls)	Yes	Yes
Status today	Online · 2770 ms	Online · 643 ms
Uptime (30 days)	Up	Up
Developer rating	Not rated yet	Not rated yet
Price	Free / free tier	Free / free tier

Simple REST API for checking working, non-working or short days for Russia, CIS, USA and other.

API производственного календаря

Strengths

Public holidays for US states and 30 countries plus sports and finance calendars as static JSON.

Free static JSON API: US/world public holidays, FOMC dates, sports and finance calendars. CORS-open, no auth, no rate limit.

Strengths

Prototyping or a tutorial? Pick the one that needs no API key (both qualify).
Calling from a web page? You need CORS. Otherwise route requests through your own server or a serverless function.
Going to production? Favour HTTPS, a strong uptime record and a provider with clear rate limits and terms. Check each API's docs before you commit.
Still unsure? Both are free to try: send one request to each and compare the data you get back.

Neither needs an API key; you can call both straight away.