shipapis
StarSubmit an APISubmit API

Nexmo API vs TwitterApi.IO

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

APINexmo APINEW—TwitterApi.IOREACHABLE—
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 limit10, 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 1Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Nexmo API vs TwitterApi.IO: common questions

Which is more reliable, Nexmo API or TwitterApi.IO?

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

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

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

Are Nexmo API and TwitterApi.IO free for commercial use?

Nexmo API has unclear commercial terms, and TwitterApi.IO 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.