Find the verified work email behind a LinkedIn profile URL, with the person’s name, headline and current company attached.
13 credits/ call
RestrictedNever more than 20 credits a call.
You only pay when data comes back.
curl -X POST "https://api.primaryapi.com/v1/run/linkedin.email" \
-H "Authorization: Bearer $PRIMARYAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"profileUrl":"https://www.linkedin.com/in/williamhgates"}'{
"output": {
"found": true,
"data": {
"email": "<string | null>",
"firstName": "<string | null>",
"lastName": "<string | null>",
"headline": "<string | null>", …
}
},
"credits": 13
}Input and output
1 field
https://www.linkedin.com/in/williamhgat….7 fields
Good to know
Needs approval. This API returns personal data. Your account needs approval, and you accept the permissible-purpose terms, before a key can call it. Calls made before that are refused and never charged. Restricted: needs an approved account and an accepted permissible purpose. Public LinkedIn data only. LinkedIn’s User Agreement restricts automated collection and LinkedIn enforces it; use the data for lawful purposes, keep copies only as long as you need them, and treat post and article text as the author’s content (analysis, not republication). Results contain personal data about identifiable people (GDPR, UK GDPR, CCPA): have a lawful basis, honour deletion requests, and never use it for spam or unsolicited bulk outreach. Email discovery is regulated personal-data processing (GDPR, CCPA, CAN-SPAM, PECR). Request access →
Addresses are SMTP-checked.
When the profile exists but no address is found. The call succeeds with email null and is billed, because the search itself was run.
A profile that does not exist is a miss.
Validate addresses before sending.
The same key and credits work for every API.