shipapis
StarSubmit an APISubmit API

Findwork vs Namedays Calendar

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

APIFindworkHEALTHY95Namedays CalendarHEALTHY89
Uptime · 30d
Uptime · 90d100%92.1%
Uptime · 30d100%98.3%
P50 · ms269536
P95 · ms17932749
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limit4294967295 req/window · 4294967295 remaining · resets 060 req/window · 58 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

Findwork vs Namedays Calendar: common questions

Which is more reliable, Findwork or Namedays Calendar?

On our scheduled checks, Findwork leads on measured uptime — Findwork at 100% versus Namedays Calendar at 92.1% 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, Findwork or Namedays Calendar?

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

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

Can I call Findwork and Namedays Calendar from the browser?

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

Are Findwork and Namedays Calendar free for commercial use?

Findwork 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.