shipapis
StarSubmit an APISubmit API

BulkSMS JSON REST API vs Nager.Date

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

APIBulkSMS JSON REST APINEW—Nager.DateNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree, no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

BulkSMS JSON REST API vs Nager.Date: common questions

Which is more reliable, BulkSMS JSON REST API or Nager.Date?

On our scheduled checks, Nager.Date leads on measured uptime — BulkSMS JSON REST API at —% versus Nager.Date at —% 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 Nager.Date need an API key?

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

Can I call BulkSMS JSON REST API and Nager.Date from the browser?

Only Nager.Date 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 Nager.Date free for commercial use?

BulkSMS JSON REST API has unclear commercial terms, and Nager.Date 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.