Phone number validation that checks the line before you dial.

Each lookup returns a structured result for the number: the normalized national number, the country (geolocation), the line type (MOBILE, LANDLINE, or VOIP), the current carrier, whether the number has been ported, and the previous carrier when it has. A status code (IdError) tells you whether the number is valid, with 1 meaning valid. That is enough to answer the questions that matter before you dial or text: is this a real, assigned number? Can it receive SMS? Which network is it on? Has it moved since you collected it?

Only mobile numbers can reliably receive text messages. Sending SMS to a landline wastes a message credit with your SMS provider and never reaches the customer. Two-factor authentication codes, delivery notifications, and appointment reminders all fail silently the same way. Line type also matters for compliance: US rules treat automated calls and texts to mobile numbers differently from calls to landlines. VOIP numbers are often used for temporary or virtual lines, so many teams flag them for review at signup to limit fraud. With the line type on every record, you can route mobiles to SMS, landlines to voice or email, and review VOIP numbers before they enter your CRM.

A ported number is one the owner kept when they switched carriers. For example, a number first issued by AT&T may now be on T-Mobile. Porting is common, and it matters because any routing, pricing, or fraud logic based on the original carrier will be wrong. DQVerify returns a Ported flag, the current operator, and the previous operator when one exists, so your data reflects where the number actually lives today. For fraud teams, a recent port on an account that is about to reset a password or change a payout destination can be a warning sign worth a second look. For marketing and operations teams, knowing the current carrier helps with SMS deliverability and cost planning.

Send the number in international E.164 format (for example +12125550101) or in local format. When you use E.164, the country is detected automatically from the dialing prefix. For local numbers, add a country field such as "USA" so DQVerify knows how to read the digits. The response always includes the normalized number, so you can store one consistent format across your CRM, whatever format customers typed. Validation covers international numbers as well as the US. That is useful for global signup forms and for contact lists collected across several markets. The same endpoint and response format apply in every country, so your integration code does not change by region.

For real-time checks, send a POST request with the number to /api/external/validate/phone, using your API key as a Bearer token. Responses return in under 150 ms at the 95th percentile, fast enough to check a number while a customer is still filling in a form. The same key works for the address and email endpoints, so one integration covers all three. For existing lists, upload a CSV in the dashboard, map the phone column, and download an enriched file with line type, carrier, and status added to every row. Files under 50,000 rows typically finish in under ten minutes. Inputs are processed in real time and not retained, and batch results are deleted after your session.

Each phone lookup costs one credit. Every account starts with 1,000 free credits and no credit card is required, so you can test on your own numbers first. That's 1,000 instead of the usual 100, for sign-ups until Nov 30, 2026. After that, mobile credit packs start at $300 for 20,000 credits, with volume tiers up to 500,000. Phone credits are priced per module because carrier data comes from licensed telecom databases that charge per query. There is no subscription and no auto-renewal, and paid credits are valid for one year. Phone credits cover phone lookups; address and email checks use their own packs with the same API key. The calculator on the pricing page shows the exact per-credit cost for your volume.