Namedays Calendar vs The SMS Works API

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

Uptime · 30d
Uptime · 90d91.2%100%
Uptime · 30d85.0%100%
P50 · ms480518
P95 · ms27491101
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limit60 req/window · 58 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Namedays Calendar vs The SMS Works API: common questions

Which is more reliable, Namedays Calendar or The SMS Works API?

On our scheduled checks, The SMS Works API leads on measured uptime — Namedays Calendar at 91.2% versus The SMS Works API at 100% 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, Namedays Calendar or The SMS Works API?

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

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

Can I call Namedays Calendar and The SMS Works API from the browser?

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

Are Namedays Calendar and The SMS Works API free for commercial use?

Namedays Calendar has unclear commercial terms, and The SMS Works 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.