greatapis

Phone — entry 001 of 7

Numlookup

Verified Jul 2026

Numlookupapi.com (an Everapi GmbH product) validates phone numbers and returns formatting, country, location, carrier, and line type via a REST endpoint that takes the number as a path parameter. A live OPTIONS preflight against its real API host, api.numlookupapi.com/v1/validate/, returned access-control-allow-origin echoing the request Origin plus access-control-allow-credentials: true, resolving the stored "unknown" cors to "yes"; a follow-up unauthenticated GET returned a 401 with www-authenticate: Key and a missing_api_key JSON error, confirming auth "API Key" over HTTPS. Its pricing page offers a Free plan (100 requests/month) alongside paid Basic/Pro/Scale tiers — freemium.

phone-validationcarrier-lookupline-typeopenapifreemium
Visit numlookupapi.com ↗Read the docs ↗Pricing ↗More Phone
AuthenticationAPI KeySign up with the provider to obtain credentials.
HTTPSSupportedTraffic is encrypted in transit.
CORSEnabledCallable directly from browser JavaScript.
PricingFreemiumA usable free tier exists, with paid plans for more volume.
FormatsJSONResponses can be requested as JSON.

GreatAPIs Score

Score81out of 100
Authentication15/25API key required
Pricing17/20Freemium tier available
Docs20/20Machine-readable spec file bundled
Formats9/15Single response format
Freshness20/20Verified within 6 months

Embed this badge

Scored 81 on greatapis.com
<a href="https://greatapis.com/api/numlookup/"><img src="https://greatapis.com/badge/numlookup.svg" alt="Scored 81 on greatapis.com"></a>

Auth quickstart

  1. Get a key at the provider
  2. Send it on every request as a headerAuthorization: <key>
  3. The exact header isn't documented — Authorization is a common default; confirm in the provider's docs.
Stored keyNo key stored

Your key is stored only in this browser (localStorage) and sent directly to the API — never to greatapis.

Endpoints

Servers
https://api.numlookupapi.com
Auth
ApiKeyQueryApiKeyHeader
Validation1

Phone number validation.

GET/v1/validate/{number}Validate a phone number
Parameters
NameInRequiredType
numberpathyesstring
country_codequerynostring
Responses
StatusDescriptionSchema
200Validation result. Check the `valid` field.ValidationResult
401——
422——
429——
500——
Metadata1

Account status.

GET/v1/statusAccount quota status
Responses
StatusDescriptionSchema
200Current quota usage for the authenticated account.StatusResponse
401——

Try it

Developer reference
Base URLhttps://api.numlookupapi.com
Rate limit
100 requests/month plus 10 requests/minute on Free plan; 5,000/month on Basic; 50,000/month on Pro; 250,000/month on Scale; custom on Enterprise
Key endpoints
  • GET/v1/validate/{number}
  • GET/v1/status
Featured in
2 collections
Spec-backed APIsCORS-ready browser APIs
People comparing Numlookup also look at…
All 7 →
Numlookup vs Phone Specification
Phone Specification needs no API key, while Numlookup requires API Key — pick Phone Specification to start without signup.
Compare →
Numlookup vs Cloudmersive Validate
Cloudmersive's Phone Number Validation API parses and standardizes global phone numbers, returning line type, E.164/international/national formats, and country data, with client libraries for over 10 languages. A live OPTIONS preflight against its real API host, api.cloudmersive.com/validate/phonenumber/basic, returned Access-Control-Allow-Origin: * (cors reconfirmed "yes"), and a follow-up unauthenticated POST returned a 401 "Invalid API key or exceeded limits" over HTTPS, reconfirming auth "API Key" and https true. Its pricing page offers 600 free calls/month with no expiration alongside a $2,000/month paid tier — freemium.
Compare →
Numlookup vs Numverify
Numverify (an APILayer product) validates phone numbers against international numbering-plan rules and returns carrier, line type, and location data for 232 countries. Its documented base endpoint, apilayer.net/api/validate, answered a live GET with a 200 JSON body carrying access-control-allow-origin: * — resolving the stored "unknown" cors to "yes" — and rejected the request with an invalid_access_key error, confirming auth "API Key"; the same endpoint also answers on https://, confirming the stored https true even though the docs quote the base URL as plain http://. Its pricing page offers a free-forever plan (100 requests/month) alongside paid Basic/Professional/Enterprise tiers — freemium.
Compare →
Numlookup vs Phone Validation
AbstractAPI's Phone Validation API checks whether a number is real, and returns its carrier, line type, risk score, and registered location, from a single GET request. The stored url redirected (301) to /api/phone-validation-api, now recorded as the canonical link. A live GET against its real host, phonevalidation.abstractapi.com/v1/, returned Access-Control-Allow-Origin: * (cors reconfirmed "yes") and a 400 validation error demanding the api_key parameter, confirming auth "API Key" over HTTPS. Its landing page advertises 100 free requests with no credit card required, ahead of paid usage tiers — freemium.
Compare →
Numlookup vs Veriphone
Veriphone validates phone numbers and returns carrier, line type (mobile/fixed/VoIP), and formatted output for 243 countries, either via a single lookup or bulk CSV upload. Its own docs state "CORS is enabled on all endpoints," and a live OPTIONS preflight plus an unauthenticated GET against api.veriphone.io/v3/verify both returned Access-Control-Allow-Origin echoing the request Origin, reconfirming cors "yes"; the GET also returned a 400 JSON error demanding the key parameter, reconfirming auth "API Key" over HTTPS. Its pricing page offers 1,000 free validations/month with no credit card required, alongside one-time credit packs and monthly subscription tiers — freemium.
Compare →
Numlookup vs VeriRoute Intel
Numlookup is freemium, while VeriRoute Intel is metered — Numlookup is the cheaper way in.
Compare →