shipapis
StarSubmit an APISubmit API

The SMS Works API vs Vonage (Nexmo) API

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

APIThe SMS Works APINEW—Vonage (Nexmo) APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublished10, 120;w=60;name="crd|generic_key^nexmo-gloo.sanity-service-remote-address-120-rpm|remote_address", 10;w=1;name="crd|generic_key^nexmo-gloo.sanity-service-remote-address-10-rps|remote_address" req/window · 9 remaining · resets 1
In directory since2026-07-052026-07-05
operationalpartialdownno data

The SMS Works API vs Vonage (Nexmo) API: common questions

Which is more reliable, The SMS Works API or Vonage (Nexmo) API?

On our scheduled checks, Vonage (Nexmo) API leads on measured uptime — The SMS Works API at —% versus Vonage (Nexmo) API 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 The SMS Works API and Vonage (Nexmo) API need an API key?

Both ask you to authenticate — The SMS Works API uses an API key and Vonage (Nexmo) API uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call The SMS Works API and Vonage (Nexmo) API from the browser?

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

Are The SMS Works API and Vonage (Nexmo) API free for commercial use?

The SMS Works API has unclear commercial terms, and Vonage (Nexmo) 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.