shipapis
StarSubmit an APISubmit API

Hebrew Calendar vs Public Time API

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

APIHebrew CalendarNEW—Public Time APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
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 Public Time API: common questions

Which is more reliable, Hebrew Calendar or Public Time API?

On our scheduled checks, Public Time API leads on measured uptime — Hebrew Calendar at —% versus Public Time API at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Hebrew Calendar and Public Time API need an API key?

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

Can I call Hebrew Calendar and Public Time API from the browser?

Only Hebrew Calendar is browser-friendly — it returns CORS headers over HTTPS. Public Time API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Hebrew Calendar and Public Time API free for commercial use?

Hebrew Calendar has unclear commercial terms, and Public Time 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.