Vonage (Nexmo) API vs The Calendar

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (US federal list per 5 U.S.C. § 6103)
Free tierFree tier — API key requiredFree, no auth (per site)
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 1None stated (site advertises no rate limit)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Vonage (Nexmo) API vs The Calendar: common questions

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

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

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

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

Only The Calendar 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 The Calendar free for commercial use?

Vonage (Nexmo) API has unclear commercial terms, and The Calendar 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.