REST API · $0.0025 per lookup
Phone verification API with real-time lookup
One POST request tells you whether a phone number is live — line status, carrier, and registration signals in under a second. Drop it into checkout, signup, or OTP flows and stop fake numbers before they enter your database.
One request, one answer
No SDKs to install, no webhooks to configure for the basics. Send the number, get the verdict.
Request
curl -X POST https://truereach.one/v1/verify \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"phone": "+5511999990001"}'Response
{
"phone": "+5511999990001",
"status": "active",
"checked_at": "2026-10-19T11:00:00Z"
}
// status: active | inactive | unknownWhere teams put it
Checkout validation
Catch typos and fake numbers the moment the customer submits the form. For COD stores, this single check prevents the most expensive failure in the funnel — shipping to nobody.
Signup & OTP flows
Verify the number is real before you pay to send the OTP. Filters out disposable and dead numbers that inflate your messaging bill.
CRM hygiene
Run nightly or weekly sweeps over new contacts so sales and support always work from numbers that can actually be reached.
What "HLR lookup" actually tells you
A Home Location Register lookup queries the mobile network itself to ask: does this number exist, is it switched on, which carrier serves it, and has it been ported? It's the closest thing to asking the network directly — no message sent, no user interaction needed.
Read the full explainer: HLR lookup, explained →Simple, per-lookup pricing
Trial
Free
800 API lookups after account review. No credit card.
Pay as you go
$0.0025 / lookup
Top up from $1. Credits never expire.
Volume
$400 / 1.2M credits
≈240,000 lookups. Best rate for high-volume pipelines.
Cleaning an existing list instead? Bulk verification handles 2,000–2,000,000 numbers per task →
Frequently asked questions
- What data does the phone verification API return?
- Each lookup returns the phone number, its verification status (active, inactive, or unknown), and the check timestamp. Status is derived from live line and registration signals, including HLR-style carrier data where available.
- How fast is a single lookup?
- Typically under one second. The endpoint is designed for synchronous use in checkout, signup, and OTP flows where you need an answer before the user moves on.
- How much does the API cost?
- $0.0025 per successful lookup (5 credits). Every account receives 4,000 free credits after review — enough for 800 free API lookups. Volume packs bring the effective rate down further.
- Is there a rate limit?
- Yes — 30 requests per minute per IP on the single-lookup endpoint, which is generous for checkout and form-validation flows. For large lists, use bulk verification instead: it handles 2,000 to 2,000,000 numbers per task asynchronously.
- How do I authenticate?
- With a bearer token issued when your account is approved for API access. Pass it in the Authorization header on every request. Business accounts can rotate keys from the dashboard.
- Can I use this at checkout to block fake numbers?
- That's one of the most common use cases. Call the API when the customer submits their phone number: if the status comes back inactive, prompt them to correct it before the order is placed. COD sellers use this to cut failed deliveries at the source.
Add real-time verification to your stack
Get API credentials after a quick manual review. Your first 800 lookups are on us.
No credit card required · Manual review, usually within hours