shipapis
StarSubmit an APISubmit API

Bufferapp vs Vonage (Nexmo) API

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

APIBufferappNEW—Vonage (Nexmo) APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSnono
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

Bufferapp vs Vonage (Nexmo) API: common questions

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

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

Both ask you to authenticate — Bufferapp 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 Bufferapp and Vonage (Nexmo) API from the browser?

Neither sends browser-friendly CORS headers reliably, so call Bufferapp and Vonage (Nexmo) API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Bufferapp and Vonage (Nexmo) API free for commercial use?

Bufferapp 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.