Mobile / Phone Number Finder avatar

Mobile / Phone Number Finder

Pricing

from $100.00 / 1,000 lead submissions

Go to Apify Store
Mobile / Phone Number Finder

Mobile / Phone Number Finder

Input: LinkedIn profile URL, OR first name + last name with company name or company domain. Get: direct mobile numbers.

Pricing

from $100.00 / 1,000 lead submissions

Rating

5.0

(2)

Developer

Scalelist

Scalelist

Maintained by Community

Actor stats

3

Bookmarked

886

Total users

291

Monthly active users

4 days ago

Last modified

Categories

Features

Limited permissionsMulti-tenantServer interface

Share

Bulk Phone Finder by Scalelist

Find verified mobile numbers for any list of leads — from a LinkedIn profile URL alone, or from a name and company.

Powered by Scalelist — the email and phone finder used by over 30,000 users on the Scalelist web app every day.

How it works

Each lead can be identified two ways. Use whichever you have — or both together for the best match rate.

  • linkedin_profile_url on its own — no name or company needed.
  • first_name + last_name, with company_domain (preferred) or company_name to sharpen the match.

Supplying a LinkedIn profile and a name gives the highest match rate of all. You can mix both styles freely in the same list — every lead is matched independently.

Input

FieldRequiredDescription
leads[].linkedin_profile_urlEither this…Full LinkedIn profile URL. Sufficient on its own
leads[].first_name…or this pairLead's first name
leads[].last_name…or this pairLead's last name
leads[].company_domainOptionale.g. acmecorp.com — preferred over company name
leads[].company_nameOptionalUse if the domain is unknown

Every lead needs either a linkedin_profile_url or both first_name and last_name. Leads with neither are skipped with a warning; the rest of the run continues.

Example input

{
"leads": [
{
"linkedin_profile_url": "https://www.linkedin.com/in/arnaud-renoux-129aa949/"
},
{
"first_name": "Youssef",
"last_name": "El Kaddioui",
"company_domain": "scalelist.com",
"linkedin_profile_url": "https://www.linkedin.com/in/youssefelkaddioui/"
},
{
"first_name": "Arnaud",
"last_name": "Renoux",
"company_name": "Scalelist"
}
]
}

Output

One row is written to the Apify Dataset for every lead — giving you a complete record of the run.

FieldTypeDescription
first_namestring | nullLead's first name, if supplied
last_namestring | nullLead's last name, if supplied
company_domainstring | nullCompany domain used for the lookup
company_namestring | nullCompany name used for the lookup
linkedin_profile_urlstring | nullLinkedIn profile URL used for the lookup
phonestring | nullFound mobile number. null if not found
phone_statusstringFound · Not found · Timeout · Submit failed
foundbooleantrue if a mobile number was found

Example output rows

Found — from a LinkedIn URL only:

{
"first_name": null,
"last_name": null,
"company_domain": null,
"company_name": null,
"linkedin_profile_url": "https://www.linkedin.com/in/arnaud-renoux-129aa949/",
"phone": "+1-555-0198",
"phone_status": "Found",
"found": true
}

Found — from a name and company:

{
"first_name": "Youssef",
"last_name": "El Kaddioui",
"company_domain": "scalelist.com",
"company_name": null,
"linkedin_profile_url": "https://www.linkedin.com/in/youssefelkaddioui/",
"phone": "+1-555-0142",
"phone_status": "Found",
"found": true
}

Not found:

{
"first_name": "John",
"last_name": "Doe",
"company_domain": null,
"company_name": "Some Company",
"linkedin_profile_url": null,
"phone": null,
"phone_status": "Not found",
"found": false
}

Call it over HTTP: one lead, one answer

Need the mobile number of one lead right now, from your own app, an AI agent or an automation? Call this Actor as a REST API. Send one lead in one HTTP request and get the result back in the response, usually within a few seconds. No run to start, no dataset to read.

  • Address: copy the Actor's URL from its Server tab in Apify Console.
  • Authentication: your Apify API token, in the header Authorization: Bearer <token>.
  • Body: one lead as JSON, with a linkedin_profile_url, or first_name and last_name with company_domain or company_name.
curl -X POST "<ACTOR_URL>" \
-H "Authorization: Bearer <APIFY_TOKEN>" \
-H "Content-Type: application/json" \
-d '{"linkedin_profile_url": "https://www.linkedin.com/in/youssefelkaddioui/"}'

The response has the same fields as a dataset row (see Output above):

{
"first_name": null,
"last_name": null,
"company_domain": null,
"company_name": null,
"linkedin_profile_url": "https://www.linkedin.com/in/youssefelkaddioui/",
"phone": "+1-555-0142",
"phone_status": "Found",
"found": true
}
HTTP statusMeaning
200Lookup done. found tells you whether a number was found
400The lead is missing fields or is not valid JSON. Fix it and send it again
502 / 503The lookup could not finish. Send the request again

To process a list of leads, start a normal run with the input above instead.

Error handling

SituationBehaviour
Lead has neither a LinkedIn profile URL nor a full nameLead is skipped with a warning; others continue
Rate limit (429)Exponential backoff, up to 5 automatic retries
Batch submit errorBatch skipped, placeholder rows written, run continues
Spend cap reachedActor stops cleanly; remaining leads are not submitted
Actor timeoutActor stops before submitting batches it can't retrieve results for

Other Scalelist Actors


Support