Skip to main content
POST
https://api.gtmapis.com
/
v1
/
people
/
email-to-linkedin
Email to LinkedIn
curl --request POST \
  --url https://api.gtmapis.com/v1/people/email-to-linkedin \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "email": "<string>",
  "enrich_profile": true
}
'
{
  "linkedin_url": "<string>",
  "profile": {},
  "found": true,
  "confidence": 123,
  "source_provider": "<string>",
  "credits_charged": 123,
  "cache_hit": true,
  "latency_ms": 123
}

Email to LinkedIn

Convert a professional email address into a LinkedIn profile URL. Useful for enriching contact lists with social profiles.

Endpoint

POST /v1/people/email-to-linkedin

Request

email
string
required
Work email address to look up
enrich_profile
boolean
default:"false"
If true, returns full profile data (adds 1 credit)

Example Request

curl -X POST https://api.gtmapis.com/v1/people/email-to-linkedin \
  -H "Content-Type: application/json" \
  -H "X-API-Key: gtm_test_your_key_here" \
  -d '{
    "email": "john.doe@acme.com",
    "enrich_profile": true
  }'

Response

linkedin_url
string
The person’s LinkedIn profile URL
profile
object
Full profile data (only if enrich_profile: true). See Profile Enrichment for fields.
found
boolean
Whether a LinkedIn profile was found
confidence
integer
Overall confidence score (0-100)
source_provider
string
Data provider that returned the result
credits_charged
integer
Credits charged for this request
cache_hit
boolean
Whether result was served from cache
latency_ms
integer
Request time in milliseconds

Success Response

{
  "linkedin_url": "https://linkedin.com/in/johndoe",
  "profile": {
    "first_name": "John",
    "last_name": "Doe",
    "full_name": "John Doe",
    "email": "john.doe@acme.com",
    "title": "Senior Account Executive",
    "company": "Acme Inc",
    "company_domain": "acme.com",
    "linkedin_url": "https://linkedin.com/in/johndoe",
    "location": "San Francisco, CA",
    "seniority": "Senior",
    "department": "Sales"
  },
  "found": true,
  "confidence": 95,
  "source_provider": "prospeo",
  "credits_charged": 4,
  "cache_hit": false,
  "latency_ms": 389
}

Not Found Response

{
  "linkedin_url": "",
  "found": false,
  "confidence": 0,
  "credits_charged": 0,
  "cache_hit": false,
  "latency_ms": 245,
  "error": "No LinkedIn profile found for email"
}

Credit Pricing

ResultCredits Charged
LinkedIn URL found3 credits
LinkedIn URL found + profile enrichment4 credits
Not found0 credits
Error / failure0 credits
Personal email addresses (Gmail, Yahoo, etc.) have lower match rates than work emails. Use work emails when possible.

Email Types

Email TypeExampleMatch Rate
Work emailjohn.doe@acme.comHigh (80%+)
Personal emailjohndoe123@gmail.comLow (20-40%)
Catch-all domaincontact@company.comVery low

Error Responses

400 Bad Request

{
  "error": "Bad Request",
  "message": "email is required"
}

401 Unauthorized

{
  "error": "Unauthorized",
  "message": "Invalid API key"
}

503 Service Unavailable

{
  "error": "Service Unavailable",
  "message": "email to LinkedIn lookup not configured"
}

Use Cases

Add LinkedIn URLs to your CRM records for better social selling.
Enhance purchased or conference lead lists with LinkedIn profiles.
Research prospects before outreach by finding their LinkedIn profiles.
Verify that email addresses belong to real people with professional profiles.