Numverify vs Poptin API

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms292698
P95 · ms14881705
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree tier — key may be required
Rate limitUnpublished120 req/window · 119 remaining
In directory since2026-07-052026-10-04
operationalpartialdownno data

Numverify vs Poptin API: common questions

Which is more reliable, Numverify or Poptin API?

Both are neck-and-neck — Numverify and Poptin API each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Numverify or Poptin API?

Numverify has the lower median latency in our checks — Numverify responds in 292 ms versus Poptin API at 698 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Numverify and Poptin API need an API key?

Both ask you to authenticate — Numverify uses an API key and Poptin 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 Numverify and Poptin API from the browser?

Only Poptin API is browser-friendly — it returns CORS headers over HTTPS. Numverify needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Numverify and Poptin API free for commercial use?

Numverify has unclear commercial terms, and Poptin 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.