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_phone": "+15551234567",
"last_validated_at": "2026-03-04"
}
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:
Parameter | Type | Use |
| string | One profile |
| array | Up to 100 profiles in a single call |
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.
{
"linkedin_urls": [
"https://linkedin.com/in/person-one",
"https://linkedin.com/in/person-two"
]
}For lists longer than 100, chunk into batches of 100 and pause briefly between them rather than firing everything at once.
Qualify before you enrich
Because this is the priciest per-result lookup, it pays to narrow the list before calling it rather than after. Run your filters first and enrich only the contacts you’d actually call:people search
search_peoplewithseniority,department, and location filtersReview
results.totaland tighten until the list is the size you intend to workBatch the resulting LinkedIn URLs into
linkedin_to_mobile_phone, 100 at a time
Enriching a 5,000-row list “just in case” is how an external token balance 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.
Screen against DNC yourself
MoltSets does not currently provide Do Not Call status. No field in the response indicates whether a number is on a DNC registry, and a returned number is not a number that has been cleared to call.
last_validated_at confirms only that the number was active and in service on that date. It is not a permission signal. Scrubbing against the applicable DNC registries before you dial or send, and complying with the calling and messaging rules that apply to you, is your responsibility.
Practically, that means putting a DNC scrub between enrichment and outreach: take the numbers this endpoint returns, run them through your own registry check or your dialer’s built-in scrubbing, and call only what survives. The endpoint fits the enrichment step of that pipeline, not the compliance step.
Compliance beyond DNC
Beyond DNC, make sure your outreach program also accounts for:
TCPA consent: consent requirements for autodialed calls and marketing texts to mobile numbers.
State laws: many states add their own rules on calling hours, attempt limits, and text messaging.
Opt-outs: honoring requests, keeping an internal DNC list, and suppressing those numbers going forward.
Review the rules that apply to your use case, and consult your own counsel as needed.
