FinSignals API vs Nexmo API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree 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

FinSignals API vs Nexmo API: common questions

Which is more reliable, FinSignals API or Nexmo API?

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

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

Can I call FinSignals API and Nexmo API from the browser?

Only FinSignals API 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 FinSignals API and Nexmo API free for commercial use?

FinSignals API 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.