BulkSMS JSON REST API vs Namedays Calendar

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

Uptime · 30d
Uptime · 90d0.0%92.1%
Uptime · 30d0.0%98.3%
P50 · ms—536
P95 · ms—2749
AuthapiKeynone
CORSnoyes
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

BulkSMS JSON REST API vs Namedays Calendar: common questions

Which is more reliable, BulkSMS JSON REST API or Namedays Calendar?

On our scheduled checks, Namedays Calendar leads on measured uptime — BulkSMS JSON REST API at 0.0% 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.

Do BulkSMS JSON REST API and Namedays Calendar need an API key?

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

Can I call BulkSMS JSON REST API and Namedays Calendar from the browser?

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

Are BulkSMS JSON REST API and Namedays Calendar free for commercial use?

BulkSMS JSON REST 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.