Submit up to 1,000 phone numbers and get the line type back for each one, with the carrier where it resolves. The check that decides whether a number can receive an SMS at all - worth running before a campaign rather than after it fails.
This is the distinction that decides whether this service is the one you want.
What comes back describes the number: which carrier operates it and what kind of line it is. That's infrastructure information - the sort of thing a telecoms routing table knows. It is genuinely useful, and it is not what most people assume a phone lookup does.
What does not come back is anything about whoever holds the number. No name, no address, no household. If identifying the person behind a number is the job, that's a different service in the catalogue - see all services - and it carries a very different set of legal considerations.
Used for what it is, this answers a question that matters commercially: can I text this number, and who would carry the message. Send an SMS campaign to a list of landlines and you pay for every one of them.
A phone number is the entire input. There is nothing else to configure.
Numbers work in international form - the documented example is +1 281 236 8208.
One row per number you submitted - and more columns than the reference describes.
The published reference for this endpoint documents three columns. Real exports return ten: the number as you sent it, a validity flag, the line type, the carrier, a location and country, the dialling prefix, and the same number rendered in E.164, international and national formats. The data dictionary below lists all of them with how often each one actually arrives, measured across real runs rather than taken from the reference.
One number is worth knowing before you build: carrier came back on 13% of rows. The line type is the column that arrives every time. If your workflow depends on the operator name specifically, run a handful of numbers on the free tier first and see how many of yours resolve - a minute now beats a surprise later.
Four of them are the same number in different formats, which is more useful than it sounds - one of them will match whatever your CRM expects.
mobile, fixed_line, fixed_line_or_mobile, personal_number and unknown.US. Present on 80% of rows.+1.+12812368208.+1 281-236-8208.(281) 236-8208.Two things to plan around. First, carrier arrived on only 13% of rows in the sample behind this list - treat it as a bonus, not the basis of a workflow. Second, type is frequently fixed_line_or_mobile, which is a genuine "could be either" rather than a missing value: for SMS decisions that is not the same as a confirmed mobile. valid, the four format columns and country_code were present on every row.
A short field list isn't the same as a small amount of value. Here's what these two actually decide.
A text message to a landline is money spent on nothing. Splitting a list by line type before a send means you only pay to message numbers that can receive one.
Mobile numbers suit SMS; other line types suit a call. One column lets you route a mixed list into the right sequence instead of treating every number the same.
A number that returns nothing is a signal in itself - it tells you a record is likely junk before a dialler wastes an attempt on it.
The carrier name tells you which network a number sits on, which is useful when delivery problems cluster on one operator rather than across a whole list.
Carrier lookups are uneven by nature, and pretending otherwise would set you up badly.
Not every number returns a carrier. In our own testing, several perfectly valid numbers came back without carrier information while others resolved cleanly. Coverage varies by country and by operator, so build your import to treat an empty carrier as an ordinary outcome rather than an error - and don't design a workflow that stalls when one is missing.
Invalid input is flagged, not silently dropped. Submit something that isn't a usable number and you get a row back saying so, which means your output row count matches your input and you can find the bad records instead of hunting for what went missing.
Line type is a fact about the number, not a permission. Learning that a number is a mobile tells you a message can arrive. Whether you're allowed to send it is a separate question, and a strict one - see the legal note below.
Where carrier and line type earn their keep.
Most phone lists are a mix of mobiles and landlines, and the mix is invisible until you look. Running the list first lets you send SMS only to numbers that can receive it, which cuts spend and stops your delivery statistics from being quietly ruined by numbers that were never eligible.
Phone fields collect typos, placeholders and test entries. Because unusable input comes back flagged rather than dropped, one pass over a database tells you which rows are real - useful before you hand a list to a dialler or import it into a CRM.
A mixed list works better as two sequences than one. Line type gives you the split - text the mobiles, call the rest - so outreach matches the channel each number can actually support instead of defaulting everyone into the same flow.
No subscription, no minimum, no per-seat licence. Your first 500 rows are on us - after that, pay-as-you-go.
Every new account, one-time. No credit card required. All scrapers unlocked - and on this service the free rows are how you check coverage for the countries you actually care about.
Roughly $2 per 1,000 numbers - reliably less than the cost of texting the landlines you'd otherwise have messaged. One row per number makes it exact to budget.
Volume pricing, SLAs, dedicated workers and bespoke onboarding for teams re-checking a large phone database on a schedule. Tell us your numbers and we'll quote.
LIVESCRAPER10 at checkout.This service checks numbers you already hold. These two are how teams collect them in the first place.
Returns company phone numbers alongside named contacts, each with the page the number was found on. A natural upstream step - collect the numbers there, classify them here.
Gives you a company phone number from nothing but a domain, plus the firmographics to decide whether the account is worth calling before you spend a minute on it.
Phone outreach is regulated more tightly than email, and this is the part worth reading properly.
The lookup itself is unremarkable: it asks which carrier operates a number and what type of line it is. Nothing is dialled, no message is sent, and nothing about the person holding the number is collected or returned.
The sending is where the rules bite. Marketing calls and texts are governed by regimes that are stricter than their email equivalents - prior consent requirements, do-not-call and do-not-contact registers, time-of-day restrictions, and per-message penalties that make mistakes expensive. A type of mobile tells you a message would arrive. It says nothing about whether you're permitted to send it, and it is not a substitute for checking the applicable registers and consent records.
A phone number tied to an identifiable person is also personal data, so the usual transparency and erasure obligations apply to your records. On our side: nothing behind a login, no third-party trackers on the data layer, and your exports auto-delete after 30 days.
The questions we hear most. Anything else? Talk to us - humans, not bots, write the answers.
phone, valid, type, carrier, location, country, country_code, and the same number in e164, international and national formats. That is measured from real exports, not from the reference, which documents only three. Worth knowing: carrier arrived on 13% of rows, while type, valid and the format columns arrived on every row.+1 281 236 8208. If your database stores numbers in a local format, normalising them before the run is the safest approach.Paste up to 1,000 numbers and get the carrier and line type for each. Your first 500 rows are free - enough to see how well your own list resolves before you commit to anything.
A list of phone numbers looks uniform and rarely is. Mixed into any real database are mobiles, landlines, numbers that stopped working years ago and entries that were never numbers at all. The Phone Numbers Enricher sorts that out: submit up to 1,000 numbers in a run and each comes back with the carrier that operates it and the type of line it is. The documented example returns a carrier of AERIAL COMMUNICATIONS and a type of mobile - three columns in total, counting the number you submitted, which is echoed back so a large export stays aligned with the input you sent.
The distinction worth being precise about is that this service describes the line rather than the person. Which carrier runs a number and whether it is a mobile is infrastructure information, the kind a routing table holds. It contains no name, no address and nothing about the household attached to the number. That matters both practically and legally: practically because identifying a number's holder is a different service in the catalogue, and legally because owner lookups sit under a substantially heavier compliance burden than a carrier check does. Used for what it is, this answers a commercial question rather than an investigative one - can a message reach this number, and which network would deliver it.
That single line-type column is where most of the value sits. Sending SMS to a landline is spend with no possible return, and because the mix in a list is invisible until someone checks, campaigns routinely pay for messages that were never eligible to arrive. Splitting a list first means texting only the numbers that can receive a text, calling the rest, and reading delivery statistics that reflect reality instead of being dragged down by ineligible records. The carrier name adds a second, narrower use: when delivery problems cluster on one operator rather than spreading across a whole list, knowing which network each number sits on is what makes the pattern visible.
Two limits are worth stating plainly. Carrier coverage is uneven - in our own testing, several perfectly valid numbers returned no carrier while others resolved cleanly, so an empty carrier should be an ordinary outcome in your importer rather than an error condition. And unusable input is flagged rather than dropped, which is a feature: your output row count matches your input, so bad records are easy to locate. Finally, and most importantly, a line type of mobile tells you a message would technically arrive and nothing whatsoever about whether you are permitted to send it. Marketing calls and texts are governed by prior-consent requirements, do-not-call registers, time-of-day restrictions and per-message penalties that make errors costly, and none of that is displaced by a carrier lookup. Nothing here is dialled and no message is sent; we classify the line and leave the sending decision, and its obligations, with you. Start free: your first 500 rows cost nothing and need no credit card.