Church Calendar vs jobdata API

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms848640
P95 · ms19971345
AuthnoneapiKey
CORSyesno
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Church Calendar vs jobdata API: common questions

Which is more reliable, Church Calendar or jobdata API?

Both are neck-and-neck — Church Calendar and jobdata 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, Church Calendar or jobdata API?

jobdata API has the lower median latency in our checks — Church Calendar responds in 848 ms versus jobdata API at 640 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Church Calendar and jobdata API need an API key?

Church Calendar needs no key, while jobdata API requires a free API key. If you want to start calling without signup, reach for Church Calendar first.

Can I call Church Calendar and jobdata API from the browser?

Neither sends browser-friendly CORS headers reliably, so call Church Calendar and jobdata API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Church Calendar and jobdata API free for commercial use?

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