BulkSMS JSON REST API vs Disify

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

Uptime · 30d
Uptime · 90d0.0%42.2%
Uptime · 30d0.0%28.3%
P50 · ms1075
P95 · ms1679
AuthapiKeynone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublished30 req/window · 21 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

BulkSMS JSON REST API vs Disify: common questions

Which is more reliable, BulkSMS JSON REST API or Disify?

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

Do BulkSMS JSON REST API and Disify need an API key?

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

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

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

Are BulkSMS JSON REST API and Disify free for commercial use?

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