shipapis
StarSubmit an APISubmit API

Church Calendar vs TimeAPI.io

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

APIChurch CalendarNEW—TimeAPI.ioNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSnoyes
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

Church Calendar vs TimeAPI.io: common questions

Which is more reliable, Church Calendar or TimeAPI.io?

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

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

Can I call Church Calendar and TimeAPI.io from the browser?

Only TimeAPI.io 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 Church Calendar and TimeAPI.io free for commercial use?

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