How to find an email from a profile URL
Take the slug after linkedin.com/in/, send it to a work email lookup or a personal email lookup, and keep only addresses whose validation status is valid. You can do this one profile at a time with an extension or for a whole export through an API.
The only input you need is the public identifier
A LinkedIn profile URL comes in many shapes: with or without www, with a country subdomain, with tracking parameters, with a trailing slash. The part that identifies the person is the slug after /in/. For https://www.linkedin.com/in/jane-doe-example/?utm_source=x the identifier is jane-doe-example.
Parse it instead of trusting the URL as a key. Split the path, take the segment after "in", drop everything after "?" and lowercase the result. Store the identifier, not the URL, so the same person pasted three ways is one record.
Both Forager email lookups accept this slug as linkedin_public_identifier. If you already hold a Forager person id from a previous search, the personal email lookup accepts person_id instead; the work email lookup takes the identifier or a name and company domain.
Work email or personal email: decide first
They are two different lookups with two different results. The work email lookup finds the address at the person's current employer and verifies it. The personal email lookup returns only free webmail addresses the person owns; company and school domains are filtered out.
| Work email | Personal email | |
|---|---|---|
| Who owns it | The employer | The person |
| Survives a job change | No | Yes |
| Typical job | B2B outreach to someone at their current company | Recruiting, executive search, ad matching |
| Forager input | LinkedIn identifier, or name + company domain | LinkedIn identifier, or person id |
| Cost | 5 credits when an address is found | 5 credits when an address is returned |
By hand: contact info, an extension, a search
For one profile, open the Contact info panel on the profile; some people publish an address there. Browser extensions reveal an address while you browse, one profile at a time, on the vendor's own credits. Page 1 for this search is mostly lists of those extensions, such as the ZoomInfo pipeline guide (updated Oct 2026) and smartlead's list of free finders (Oct 28, 2026).
By hand is fine when you have ten profiles. It breaks at a hundred: every reveal is a click, and the exported CSV is a one-off you cannot refresh. An extension also tells you nothing about how the address was found or verified.
By API: one request per profile
For the work email, submit the identifier and poll the job. For the personal email, one request answers at once with a list of addresses, or an empty body when there is nothing left after filtering.
Work email, by identifier
curl -X POST https://api-v2.forager.ai/api/v2/{account_id}/datastorage/person_contacts_lookup/work_emails/ \ -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/v2/{os.environ['FORAGER_ACCOUNT_ID']}/datastorage/person_contacts_lookup/work_emails/", 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
{ "job_id": "7f3c…", "status": "queued" } Personal email, by identifier
curl -X POST https://api-v2.forager.ai/api/{account_id}/datastorage/person_contacts_lookup/personal_emails/ \ -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/personal_emails/", 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
[{ "email": "jane.doe@gmail.com", "email_type": "personal", "validation_status": "valid" }] Never send a domain and an identifier together in a work email request; the API refuses the combination. Pick the identifier when you have it, and use the name and domain only when you do not.
Read the validation status, then send
Every address comes with a validation_status: valid, risky, invalid or unknown. Make it a rule in your code, not a judgement in your inbox.
- valid: send.
- risky: hold. Add a second signal (a reply, a profile match, a verifier of your own) before you send.
- invalid: drop it, and do not store it as a contact.
- unknown: the check could not decide. Treat it like risky.
If you email an address and it bounces or lands, tell Forager with the work email or personal email feedback endpoint (contact_status valid or invalid). Feedback calls are free and share a budget of 60 requests a minute per account.
For an export of profile URLs
A Sales Navigator or lead-form export is a list of profile URLs. Reduce each to its identifier, dedupe, and submit the list as one bulk work email batch. Poll the batch once or give it a webhook URL.
Bulk work emails
curl -X POST https://api-v2.forager.ai/api/v2/{account_id}/datastorage/person_contacts_lookup/work_emails/bulk/ \ -H "X-API-KEY: $FORAGER_API_KEY" \ -H "Content-Type: application/json" \ -d '{"email_lookups":[{"linkedin_public_identifier":"jane-doe-example"},{"linkedin_public_identifier":"john-roe-sample"}]}'
import os, requests r = requests.post( f"https://api-v2.forager.ai/api/v2/{os.environ['FORAGER_ACCOUNT_ID']}/datastorage/person_contacts_lookup/work_emails/bulk/", headers={"X-API-KEY": os.environ["FORAGER_API_KEY"]}, json={"email_lookups": [[object Object], [object Object]]}, timeout=30, ) r.raise_for_status() data = r.json() if r.content else [] # an empty body means nothing was found
- Cache per identifier so a re-upload of the same export spends nothing.
- Your balance must cover the whole batch, or it is rejected and nothing is charged.
- For personal emails there is no batch endpoint today; loop the single lookup and back off on a 429.
What it costs, and what a miss costs
A work email lookup costs 5 credits per lookup that finds an address, single or in a batch. A personal email lookup costs 5 credits when at least one address is returned. A lookup that returns nothing costs 0 credits, and polling is free.
Vendor credit prices for the extensions on page 1 change often; check each vendor's own pricing page and note the date before you compare.
Using profile identifiers responsibly
A profile URL is a key, not a license. Forager uses the public identifier to find the person in its own dataset; the guide above never asks you to scrape a profile page. Keep the identifier, the lookup date and the validation status on the record, and honor opt-outs the same day.
The pieces this guide uses
Products
Recipes
- $5 free credits
- No credit card
- Run your sample
Questions about this guide
Can I find an email from a profile URL for free?
For a handful of profiles, yes: check the Contact info panel, or use an extension's free allowance one profile at a time. For an export, a lookup API charges per address found. A Forager lookup that finds nothing costs 0 credits.
Does this work if the person has not published their email on their profile?
Yes. The lookup uses the public identifier to find the person in Forager's dataset and returns the address it holds for them, with a validation status. It does not read the profile page.
Work email or personal email for recruiting?
Personal. A candidate rarely wants a recruiter in their work inbox, and the work address dies when they move. The personal email lookup returns webmail addresses only, each with a validation status.
What is a public identifier?
The slug after linkedin.com/in/ in a profile URL, for example jane-doe-example. It is the input both Forager email lookups accept as linkedin_public_identifier.
What does a "risky" validation status mean?
The address exists but the check could not confirm it will accept mail, often because the domain accepts every address. Hold it until you have a second signal, then send or drop. Only valid addresses belong in a first send.
What do work emails cost for teams following this guide?
Work emails: 5 credits per work email found, and a work email lookup that finds nothing costs 0 credits. That is $0.07 per work email on Starter month to month and $0.05 on Pro with yearly billing. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices
Am I charged when no work email is found?
No. A work email lookup that finds nothing costs 0 credits, so you pay for work emails 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 do I know the data is right?
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 work emails 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 work emails, 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.
Does Forager integrate with the tools we already use?
Native in Clay and Zapier, partner-built in Deepline and Cargo and called through the API from Make, n8n and your own code. Everything else connects through the REST API with one API key.
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
Related guides
Sources
- Forager docs: Candidate contact information lookup (read Nov 1, 2026)
- Forager docs: Phone number API for dialers (identifier parsing) (read Nov 1, 2026)
- Forager docs: CRM data enrichment from an email (validation statuses) (read Nov 1, 2026)
- Forager docs: Bulk work email lookup (read Nov 1, 2026)
- Forager docs: API credits and pricing (read Nov 1, 2026)
- pipeline.zoominfo.com: 10 Best LinkedIn Email Finder Tools (checked Oct 2026) (read Nov 1, 2026)
- smartlead.ai: 7 Free LinkedIn Email Finders (Oct 28, 2026) (read Nov 1, 2026)