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 simplest way to move a large list: one call for 100 profiles instead of 100 separate calls means less network overhead and fewer calls to retry. It doesn’t reduce your request count, though — each item in a batch counts as one request, hit or miss, so a batch of 100 draws 100 requests from your Fair Use requests limit.
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, which are separate from your regular token balance. One phone token is spent per returned result. Phone tokens aren’t included in any plan — you buy them through a monthly phone token subscription on the Pricing page at app.moltsets.com. It’s available on paid plans only; the free plan has no phone tokens.
Public phone token subscriptions: Unused tokens roll over month to month while the subscription stays active. Cancelling either the phone token subscription or your main plan forfeits them. See Phone tokens for proration, larger subscriptions, and cancellation. You’re only charged for results that come back — profiles with no mobile on file cost nothing, and come back as HTTP 200 with status: "not_found" rather than an error. A batch of 100 profiles can therefore spend up to 100 phone tokens, so check your balance and size batches to it rather than to the endpoint’s 100-profile ceiling. get_account and get_billing are free and never cost tokens. Check your remaining phone tokens before a large run so a job doesn’t stall halfway through.

​
Qualify before you enrich

Because phone tokens are a paid add-on, 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 the top-level total and tighten until the list is the size you intend to work (total stops counting at 10,000)
  3. Batch the resulting LinkedIn URLs into linkedin_to_mobile_phone, up to 100 at a time and within your phone token balance
Enriching a 5,000-row list “just in case” is how a month of phone tokens 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.

Phone Number Validation

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

Rate Limits

Batching, backoff, and per-plan ceilings.