Skip to main content
linkedin_to_mobile_phone is the only phone endpoint in the API. It takes a LinkedIn profile and returns a carrier-verified mobile number with the date it was last verified.

​
Mobile only, by design

Only mobile numbers are returned — no landlines, no VoIP. Every result is a real device, which is what makes the output usable for SMS and direct dial rather than a switchboard you have to navigate. The practical consequence: contacts whose only number is a desk line simply won’t return a result. A miss here isn’t a data gap so much as a filter working as intended.

​
Batch up to 100 per call

The endpoint takes either a single URL or a batch: Batching is the single highest-leverage practice here. One call for 100 profiles instead of 100 calls cuts your request count by 99%, which matters because every request counts toward your rate limit regardless of whether it returns data.
For lists longer than 100, chunk into batches of 100 and pause briefly between them rather than firing everything at once. See Rate Limits for the per-plan ceilings.

​
Budget phone tokens first

Mobile lookups draw on phone tokens, an allowance set by your plan and separate from your regular token balance. One phone token is spent per returned result.
Phone tokens by plan: You’re only charged for results that come back — profiles with no mobile on file cost nothing. A batch of 100 profiles can therefore spend up to 100 phone tokens, more than the $0, $27, and $97 allowances hold, so size batches to the allowance rather than to the endpoint’s 100-profile ceiling. get_account and get_billing are free and never cost tokens. Check your remaining allowance before a large run so a job doesn’t stall halfway through.

​
Qualify before you enrich

Because phone tokens are the scarcest thing on every plan, it pays to narrow the list before calling this endpoint rather than after. Run your people search filters first and enrich only the contacts you’d actually call:
  1. search_people with seniority, department, and location filters
  2. Review results.total and tighten until the list is the size you intend to work
  3. Batch the resulting LinkedIn URLs into linkedin_to_mobile_phone, up to 100 at a time and within your phone token allowance
Enriching a 5,000-row list “just in case” is how a phone token allowance disappears in one afternoon.

​
Read the validation date

last_validated_at is the date the number was last confirmed active and in service.
Unlike email, MoltSets does not assign a risk score or confidence grade to phone numbers. The validation date is the signal — a number confirmed last week carries more confidence than one confirmed a year ago, and it’s your call how much weight to give it. See Understanding Phone Number Validation.
Set a staleness threshold that matches the channel. Cold calling a number verified 18 months ago wastes a dial; sending SMS to one wastes money and can generate complaints.

Phone Number Validation

What the validation date does and doesn’t tell you.

Rate Limits

Batching, backoff, and per-plan ceilings.