shipapis
StarSubmit an APISubmit API

caldays vs Church Calendar

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

APIcaldaysNEW—Church CalendarNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesno
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

caldays vs Church Calendar: common questions

Which is more reliable, caldays or Church Calendar?

On our scheduled checks, Church Calendar leads on measured uptime — caldays at —% versus Church Calendar 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 caldays and Church Calendar need an API key?

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

Can I call caldays and Church Calendar from the browser?

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

Are caldays and Church Calendar free for commercial use?

caldays has unclear commercial terms, and Church Calendar 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.