shipapis
StarSubmit an APISubmit API

Vonage (Nexmo) API vs Disify

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

APIVonage (Nexmo) APIUNMONITORED—DisifyNEW—
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 — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Vonage (Nexmo) API vs Disify: common questions

Which is more reliable, Vonage (Nexmo) API or Disify?

Only Disify is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do Vonage (Nexmo) API and Disify need an API key?

Disify needs no key, while Vonage (Nexmo) API requires a free API key. If you want to start calling without signup, reach for Disify first.

Can I call Vonage (Nexmo) API and Disify from the browser?

Only Disify 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 Vonage (Nexmo) API and Disify free for commercial use?

Vonage (Nexmo) 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.