jobdata API vs Namedays Calendar

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

Uptime · 30d
Uptime · 90d100%91.2%
Uptime · 30d100%85.0%
P50 · ms640480
P95 · ms13452749
AuthapiKeynone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublished60 req/window · 58 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

jobdata API vs Namedays Calendar: common questions

Which is more reliable, jobdata API or Namedays Calendar?

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

Which is faster, jobdata API or Namedays Calendar?

Namedays Calendar has the lower median latency in our checks — jobdata API responds in 640 ms versus Namedays Calendar at 480 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 jobdata API and Namedays Calendar need an API key?

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

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

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

Are jobdata API and Namedays Calendar free for commercial use?

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