Cisco Spark vs Nexmo API

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

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

Cisco Spark vs Nexmo API: common questions

Which is more reliable, Cisco Spark or Nexmo API?

On our scheduled checks, Nexmo API leads on measured uptime — Cisco Spark at —% versus 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 Cisco Spark and Nexmo API need an API key?

Both ask you to authenticate — Cisco Spark uses an API key and 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 Cisco Spark and Nexmo API from the browser?

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

Are Cisco Spark and Nexmo API free for commercial use?

Cisco Spark has unclear commercial terms, and 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.