Number Lookup & Phone Intelligence API
Real-time HLR, MNP and line-type intelligence on any phone number - validate, route and risk-score before you send or dial, from one REST endpoint with coverage in 230+ countries.
230+
Countries covered
1,000+
Networks resolved
< 1 s
Median HLR response
What is Number Lookup & Phone Intelligence API?
Every OTP sent to a dead number, every dialler call to a disconnected line and every fraudulent signup on a virtual number costs money and erodes trust. Dollu's Number Lookup API answers the question you should be asking first: is this number real, who serves it, and is it reachable right now? A single request returns E.164 formatting, country and region, current carrier, line type, portability status and - for mobile numbers - a live network query for reachability, roaming and the serving MCC-MNC. Results arrive in well under a second from the PoP nearest your application.
Three lookup levels let you pay only for the depth you need. Format lookup validates syntax and returns country, region and number type from static numbering plans without touching an operator network. MNP lookup queries national portability databases and our own routing data to return the current serving operator for ported numbers, which is essential for correct SMS and voice routing. HLR lookup goes further, sending a live query to the home network to confirm the subscriber exists, whether the handset is currently reachable and whether it is roaming, without the subscriber seeing anything.
The same data powers phone intelligence for fraud teams. Each response can include a risk score derived from line type, VoIP or virtual-number detection, recent porting activity, reachability history and velocity across your own requests, and in supported markets SIM-swap indicators from operator APIs. Use it at signup to block disposable numbers, before high-value transactions to step up authentication, and in contact-centre routing to prioritise numbers that will actually answer.
Integration is straightforward: a REST API with JSON responses, API-key or OAuth authentication, SDKs for common languages and a batch endpoint that accepts CSV or JSON files of up to several million numbers for list cleaning, with results returned by download or webhook. Lookups are priced per query with volume tiers, cached results are free within a configurable time-to-live, and only the data required for the lookup is processed, in line with GDPR data-minimisation principles.
CPaaS request and event flow: REST in, webhooks out.
Why choose Dollu for number lookup api.
The advantages of buying from a carrier that owns its network, interconnects and operations - rather than a reseller.
Stop paying to reach dead numbers
Scrubbing lists before OTP, campaign or dialler traffic removes invalid and unreachable numbers, typically cutting wasted messaging and calling spend by double-digit percentages.
Route to the right network every time
MNP-aware routing prevents SMS and calls to ported numbers being sent to the wrong operator, improving delivery rates and avoiding surcharge fees.
Catch fraud at the front door
Detect virtual, VoIP and freshly-ported numbers at signup and before high-risk transactions, and step up verification only where the risk score warrants it.
Cleaner data, better decisions
Normalised E.164 numbers, carrier and country tags and reachability history keep CRM and analytics data trustworthy across markets.
Integrate in an afternoon
One endpoint, predictable JSON, SDKs and sample code; most teams are calling the API in production within a day of receiving keys.
Capabilities in detail.
Everything included with Number Lookup & Phone Intelligence API - the platform features, options and controls you get from day one.
- 01
Format and syntax validation
Normalise any input to E.164; return country, region, number type and dial-plan validity from continuously updated numbering plans; no per-network cost.
- 02
Mobile number portability lookup
Current serving operator and MCC-MNC for ported numbers using national porting databases and Dollu routing data, with coverage in the markets that matter for A2P and voice.
- 03
Live HLR lookup
Real-time query to the home network returning subscriber validity, reachability, roaming status, serving network and error cause codes when the number is absent or barred.
- 04
Carrier and line-type detection
Classify numbers as mobile, fixed, VoIP or virtual, toll-free, premium or pager, with the operator name and type, so you can apply the right channel and policy.
- 05
Roaming and presence signals
Identify whether a handset is roaming and on which network, useful for fraud checks, compliance rules on international messaging and travel-related engagement.
- 06
Fraud and risk scoring
Composite score built from line type, virtual-number detection, recent porting, reachability history and request velocity; SIM-swap indicators where operator APIs are available.
- 07
Batch and list hygiene
Upload CSV or JSON files of up to several million numbers; choose lookup level per job; receive de-duplicated, normalised results with status codes by download or webhook.
- 08
Caching and asynchronous delivery
Configurable time-to-live for cached results, async mode with callback for slow-network destinations, idempotency keys and rate limits you set per API key.
- 09
Dashboard and reporting
Query volumes, hit rates, error breakdowns and spend per key, per country and per lookup type; CSV and API export for finance and data teams.
How it works.
From first conversation to live traffic - a tracked, engineer-led onboarding with a named owner at every step.
- Step 01
Get your API key
Sign up in the portal, create a key with the lookup levels and rate limits you need, and load prepaid credit or agree postpaid terms.
- Step 02
Choose the lookup level
Use format lookup for cheap validation at data entry, MNP for routing decisions and HLR when you need to know a number is live before sending or dialling.
- Step 03
Integrate or batch
Call the REST endpoint from your application with our SDKs, or upload a file to the batch endpoint for one-off or scheduled list cleaning.
- Step 04
Act on the result
Suppress, route, step up authentication or tag the contact based on the response, and track savings and hit rates in the dashboard.
Who uses this and why.
Typical deployments across carriers, enterprises, platforms and contact centres.
OTP and 2FA senders
Check reachability and line type before sending a code, fall back to voice for fixed lines and block virtual numbers used for account farming.
Contact centres and diallers
Scrub campaign lists nightly to remove disconnected numbers, prioritise reachable mobiles and comply with do-not-call and reassigned-number rules.
Fintech onboarding and KYC
Validate that the number belongs to a real mobile subscriber, flag recent ports and SIM swaps and score risk before approving accounts or transactions.
Marketing list hygiene
Clean CRM and lead databases before campaigns to lift delivery rates, cut cost per message and keep sender reputation intact.
Carriers and CPaaS platforms
Embed MNP and HLR data in your own routing engine to pick the correct terminating operator and avoid misrouting penalties.
E-commerce and logistics
Verify customer numbers at checkout to reduce failed delivery notifications and returned parcels caused by wrong or dead numbers.
Technical & commercial specifications.
Key parameters at a glance. Ask us for the full service description and SLA document.
| Coverage | 230+ countries; 1,000+ mobile networks for HLR/MNP |
|---|---|
| Lookup levels | Format (offline), MNP (portability DB), HLR (live network) |
| Response fields | E.164, country, carrier, MCC-MNC, line type, ported, roaming, status |
| Latency | Format < 50 ms; MNP < 200 ms; HLR median < 1 s |
| API | REST/JSON over HTTPS; API key or OAuth 2.0; SDKs and Postman |
| Batch | CSV/JSON up to several million numbers per job; webhook on completion |
| Rate limits | Configurable per key; default 100 requests/s, higher on request |
| Caching | Configurable TTL; cached hits not billed |
| Data handling | GDPR-aligned minimisation; EU or India processing on request |
| Support | 24×7 NOC; developer support; named account manager |
How APIs / CPaaS are priced.
APIs are usage-based: per minute, per message, per verification, per participant-minute or per email - at carrier pricing, because Dollu’s own network sits underneath the endpoints.
We publish the model, not a public rate card - actual rates depend on destination, route class, volume and regulatory cost. See how every Dollu service is priced.
- Free sandbox for development and testing
- Sub-account and reseller rate decks
- Committed-spend discounts by monthly usage
- No platform fee at entry volumes
- Numbers added at rental + usage
- Billing
- Metered per unit; prepaid balance or postpaid invoicing; usage visible in real time in the portal and API
- Commitment
- None; committed monthly spend earns tiered discounts
Number Lookup API - your questions answered.
The questions customers and carriers ask us most often before they interconnect. If yours is not here, our team answers within one business day.
Still have a question?
Ask our solutions teamRelated services.
Services customers commonly combine with Number Lookup & Phone Intelligence API.
Test it on your own list.
Request an API key and free evaluation credit, run your first 1,000 lookups and see how many numbers you have been paying to reach that no longer exist.
