shipapis
StarSubmit an APISubmit API

httpSMS vs Numverify

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

APIhttpSMSNEW—NumverifyNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

httpSMS vs Numverify: common questions

Which is more reliable, httpSMS or Numverify?

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

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

Only httpSMS 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 httpSMS and Numverify free for commercial use?

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