How to find a mobile number from a profile URL
Copy the slug after linkedin.com/in/, send it to a phone number lookup, and you get back the phone numbers held for that person, or nothing. Cache the result per person, dial, and report whether the number connected so the next lookup is better.
What you are actually looking for
Three kinds of number get called "a phone number". A headquarters number reaches a switchboard. A direct dial reaches a desk, which is empty more often than not. A mobile reaches the person, wherever they are. For a rep, a recruiter or a dialer, the mobile is the one that matters, because the point is that the right person picks up.
Page 1 for this search is a list of finder tools and people-search sites. Klenty's guide (Apr 20, 2026) separates mobile, direct dial and HQ numbers, which is the right distinction; the rest of this page is about how you get from a profile to a mobile and what you do after the call.
The free routes, honestly
Some people publish a mobile in the Contact info panel of their profile or in an email signature. Company websites list switchboards, not mobiles. Asking a mutual contact works and takes a day. All three are fine for one person and useless for a list.
From URL to identifier
The lookup takes linkedin_public_identifier, the slug after /in/. Parse it from whatever shape the URL arrives in: split the path on "/", take the segment after "in", and drop any query string. For https://www.linkedin.com/in/jane-doe-example/ that is jane-doe-example.
If the person came from a Forager people search, you already hold their person id; send person_id instead and skip the parsing.
One lookup per person
Send one request. The response is a list of objects with a phone_number field; an empty list means no number was found. The API reference lists phone_number and nothing else on each item, so your code should not expect a line-type field.
Phone numbers lookup
curl -X POST https://api-v2.forager.ai/api/{account_id}/datastorage/person_contacts_lookup/phone_numbers/ \ -H "X-API-KEY: $FORAGER_API_KEY" \ -H "Content-Type: application/json" \ -d '{"linkedin_public_identifier":"jane-doe-example"}'
import os, requests r = requests.post( f"https://api-v2.forager.ai/api/{os.environ['FORAGER_ACCOUNT_ID']}/datastorage/person_contacts_lookup/phone_numbers/", headers={"X-API-KEY": os.environ["FORAGER_API_KEY"]}, json={"linkedin_public_identifier": "jane-doe-example"}, timeout=30, ) r.raise_for_status() data = r.json() if r.content else [] # an empty body means nothing was found
// illustrative values, not a record
[{ "phone_number": "+1 555-0142" }] Numbers come back in a form you can normalize to E.164 before you store them. If two numbers come back, keep both on the record and let the first connected call decide which one to show first next time.
Gold and Silver
Gold is our highest-confidence set. Silver is a larger set that includes every Gold number, so choosing Silver adds numbers and never removes one.
Pick per request. Gold when the call has to connect on the first try, for example a live transfer. Silver when reach matters more than a second attempt, for example a candidate you will also email. Because Silver contains Gold, switching a request from Gold to Silver can only add numbers.
Dial, then report the outcome
After the call, tell Forager what happened. The phone number feedback endpoint takes phone_number and a contact_status of connected or disconnected, with an optional is_correct_person flag (true, false, or left out when you could not tell) and the person_id the number came from. A dialer can send it automatically after every call.
Report the outcome
curl -X POST https://api-v2.forager.ai/api/{account_id}/datastorage/feedback/phone_numbers/ \ -H "X-API-KEY: $FORAGER_API_KEY" \ -H "Content-Type: application/json" \ -d '{"phone_number":"+15550142","contact_status":"connected","is_correct_person":true,"person_id":123}'
import os, requests r = requests.post( f"https://api-v2.forager.ai/api/{os.environ['FORAGER_ACCOUNT_ID']}/datastorage/feedback/phone_numbers/", headers={"X-API-KEY": os.environ["FORAGER_API_KEY"]}, json={"phone_number": "+15550142", "contact_status": "connected", "is_correct_person": True, "person_id": 123}, timeout=30, ) r.raise_for_status() data = r.json() if r.content else [] # an empty body means nothing was found
// illustrative values, not a record
201 Created Feedback calls are free and share a budget of 60 requests a minute per account. Numbers are normalized to E.164 on the way in, so send them in any format.
Inside a dialer or an ATS
- Keep the API key on your server. The browser sends the profile URL to your backend; your backend calls Forager.
- Cache the result per person with the lookup date, so a rep who reopens a record does not spend again.
- Make the "Get number" action idempotent: a double click is one lookup.
- Handle three outcomes in the UI: numbers, no number found, and an error you can retry (429 with backoff; 403 means fix the key, do not retry).
What it costs
A phone number lookup costs 15 credits per mobile found. A lookup that returns nothing costs 0 credits. Feedback calls and polling are free.
Calling responsibly
Mobiles are personal data, and calling rules differ by country and by state. Check do-not-call lists where they apply, keep a record of consent or lawful basis, and stop calling a number the moment someone asks. Report disconnected and wrong-person numbers so they do not come back.
The pieces this guide uses
Products
Recipes
- $5 free credits
- No credit card
- Run your sample
Questions about this guide
Does the lookup return mobile numbers only?
It returns the phone numbers held for that person, as a list of phone_number values. The API reference does not document a line-type field, so treat every number as one to dial and report the outcome, which is how the data improves.
Can I find a mobile number from a name instead of a profile URL?
Yes, in two steps. Run a person role search with the name and company domain to get the person id, then send person_id to the phone numbers lookup. The guide on finding the employees of a company shows the search.
What if two numbers come back?
Keep both on the record. Dial the first, report connected or disconnected, and show the connected one first next time. A disconnected report is the signal that removes a dead number from your list.
Is it legal to find and call a mobile number in the EU or the US?
Rules differ by country and state: consent, legitimate interest, do-not-call registries and calling hours all apply. Keep a record of your basis, check the registries that apply to you, and honor every request to stop. Bring the details to a call with our team.
Why did the lookup return nothing, and was I charged?
Nothing came back because Forager holds no number it would stand behind for that person. You were not charged: a mobile lookup that returns nothing costs 0 credits. Try the person id if you sent an identifier, then move on.
What is the difference between Gold and Silver?
Gold is our highest-confidence set. Silver is a larger set that includes every Gold number, so choosing Silver adds numbers and never removes one. You choose per request on any plan.
What do mobile numbers cost for teams following this guide?
Mobile numbers: 15 credits per mobile number found, and a mobile number lookup that finds nothing costs 0 credits. That is $0.20 per mobile number on Starter month to month and $0.15 on Pro with yearly billing. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices
Am I charged when no mobile number is found?
No. A mobile number lookup that finds nothing costs 0 credits, so you pay for mobile numbers we find. Search, enrichment and reverse lookups are the exception: they are charged per request.
Is there a free way to try Forager?
Yes. Create a free account at app.forager.ai: it comes with $5 in free credits and an API key, and there is no credit card to sign up. Run it on records you already know, or book a demo and send us a list: we run it and show you what we find.
How accurate is Forager data?
Forager ranked #1 of 10 in Clay's 2026 test of mobile data providers, by quality score: Clay's measure of how likely a dialled number reaches the right person. The test that counts is your own: send a list of profiles you care about. We run it and show you what we find, number by number, so you can measure hit rate and connect rate yourself.
Where does Forager data come from, and is it compliant?
Bring your legal and security questions to a call with our team, and we take you through how Forager data is sourced and the terms that cover mobile numbers for teams following this guide. Forager's privacy policy is public, and anyone can send a request about their own personal data through the consumer rights form on forager.ai.
Is there a contract or minimum commitment?
No contract to start: a free account comes with $5 in credits. To keep using mobile numbers, choose a monthly or yearly plan. Monthly plans cancel anytime and unused credits roll over; yearly plans grant all credits upfront and cost 10% less. Larger volumes are agreed with our team.
Written answers are not available right now. The matching pages above still help, or book a demo and ask the team.
- $5 free credits
- No credit card
- Run your sample
Keep reading
Glossary
Tools
Best-of guides
Related guides
Sources
- Forager docs: Phone number API for dialers (read Nov 1, 2026)
- Forager docs: Find phone numbers with the API (read Nov 1, 2026)
- Forager docs: Report bad contact data (read Nov 1, 2026)
- Forager docs: API errors and rate limits (read Nov 1, 2026)
- Forager docs: API credits and pricing (read Nov 1, 2026)
- klenty.com: How to Find Someone's Phone Number (Apr 20, 2026, updated Jul 8) (read Nov 1, 2026)
- datablist.com: Find phone number from name (Oct 26, 2026) (read Nov 1, 2026)