Numverify
Numverify — free tier with API key
Numverify exposes a free-tier JSON API. Register for an API key if required; we verified a public or demo endpoint.
GET https://numverify.com/healthz
{
"success": true,
"service": "portal",
"hostname": "portal-main.ip-10-128-201-196.apilayer.net",
"version": "d06ac150",
"environment": "apilayer-core-production",
"deploy_datetime": "2026-07-01T11:21:26Z"
}curl "https://numverify.com/healthz"const res = await fetch("https://numverify.com/healthz");
const data = await res.json();
console.log(data);import requests
res = requests.get("https://numverify.com/healthz")
print(res.json())BROWSER CALLS BLOCKED (NO CORS/HTTPS) — USE THE CURL SNIPPET
/healthzPROBEDNumverify — free tier with API key
/pingLightweight ping endpoint.
/statusService status metadata.
We probe a documented GET and expect 2xx JSON — full uptime and health score. Export includes every documented route below.
Stable. No schema drift observed since monitoring began — the response shape has not changed under our checks.
Numverify: common questions
Is Numverify free to use?
Yes — Numverify is a free developer tools API. Free tier: Free tier — key may be required. Whether the free tier allows commercial use is unclear — check the provider docs.
Does Numverify need an API key?
Yes — Numverify needs a free API key, which you pass on each request. Rate limits: Unpublished.
Can I call Numverify from the browser?
Not directly — Numverify doesn't send browser-friendly CORS headers, so call it from a server or proxy instead. Copy the curl or Python snippet on this page to get started.
Is Numverify up right now?
As of our last scheduled check, Numverify is healthy with 100% uptime over 90 days and a 449 ms median response. We re-probe it every sweep — the status badge and uptime chart above always show the latest.