Hebrew Calendar vs OpenHolidays API

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms533533
P95 · ms20163920
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Hebrew Calendar vs OpenHolidays API: common questions

Which is more reliable, Hebrew Calendar or OpenHolidays API?

Both are neck-and-neck — Hebrew Calendar and OpenHolidays API each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Hebrew Calendar or OpenHolidays API?

They're evenly matched on speed — both Hebrew Calendar and OpenHolidays API post a 533 ms median (P50) in our checks. Look at the P95 row above if worst-case latency matters more than the typical response for your use case.

Do Hebrew Calendar and OpenHolidays API need an API key?

Neither needs a paid key — Hebrew Calendar is callable with no signup, and OpenHolidays API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Hebrew Calendar and OpenHolidays API from the browser?

Yes — both Hebrew Calendar and OpenHolidays API send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Hebrew Calendar and OpenHolidays API free for commercial use?

Hebrew Calendar has unclear commercial terms, and OpenHolidays API has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.