LinkedIn Profile to Email API — Profile Plus Address
Send a full profile URL and this source returns the professional record — name, headline, profile URL, location and about text — together with the email address where one is available.
{
"session_id": "e5b8…",
"kind": "linkedin_email",
"username": "https://www.linkedin.com/in/example/",
"human": "Jane Doe, Head of Revenue Operations…",
"machine": {
"total_items": 1,
"first_item": {
"basic_info": {
"fullname": "Jane Doe",
"headline": "Head of Revenue Operations",
"profile_url": "https://www.linkedin.com/in/example",
"location": { "full": "Austin, Texas" },
"about": "…"
},
"email": "jane.doe@acme.com"
}
},
"total_points": 10
}- You send
- A full profile URL
- You get back
- The professional record with the email address where available
- Coverage
- People with a public profile, worldwide.
- Price
- 10 pts — $10 per 1,000
- Charged only when the profile resolves. A profile that cannot be read is not billed.
Ways to get this data
Three approaches teams use today, and where each one runs into trouble.
| Approach | What it takes | Cost | Trade-off |
|---|---|---|---|
| Two tools, two steps | Read the profile, then run a finder against the domain | Two subscriptions | Two integrations and two failure modes for one outcome |
| Guessing the address from the name | Construct it from a pattern | Free | A wrong guess costs you sender reputation, which is expensive |
| NeuralVerge | One request | $10 per 1,000, misses not billed | The address comes back when it can be resolved — it is not guaranteed on every profile |
What you get back
Every field in the response shown above.
| Field | Type | Description |
|---|---|---|
total_items | number | How many records came back. |
basic_info.fullname | string | The person's full name. |
basic_info.headline | string | Their headline. |
basic_info.profile_url | string | The profile URL. |
basic_info.location | object | Where they are based. |
basic_info.about | string | The about text. |
email | string | The email address, returned when one can be resolved. |
How to run it
The same lookup works from the app, the API, or as a tool an agent can call mid-task.
The `username` parameter takes the full profile URL, not a bare handle. One profile per request.
curl -X POST https://api.neuralverge.ai/functions/v1/run-linkedin-email \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "username": "https://www.linkedin.com/in/example/" }'What teams use it for
Where this field shows up in an actual workflow.
Go from a list of profiles to a list of contactable people in one pass.
Someone gave you their profile; this gets you the way to reply.
Reach a candidate outside a platform's own messaging.
Attach an address to a contact you only have a profile for.
Coverage, freshness and limits
What this source covers, how fresh it is, and where it stops.
People with a public profile, worldwide.
Read at request time.
This source returns personal data. Use it for legitimate business purposes under your own lawful basis, honour deletion and opt-out requests, and check the acceptable use policy for what is out of bounds.
- —The email is returned where it can be resolved, which is not every profile.
- —Private or restricted profiles will not resolve at all.
- —A resolved address is not a validated one — run Email validation before a large send.
Questions, answered
No. The address is returned where it can be resolved. When it cannot, you still get the profile record and can fall back to Email finder with the name and the company domain.
Related sources
Try linkedin people profile + email on your own data
One request format across every source in the catalog.