Can Proxycurl's Person Profile Endpoint Return Contact Information?
You have questions. We have answers. This time about contact information enrichment.

/ proxycurl

Does Proxycurl’s Third-Party LinkedIn API Scrape Contact Information From LinkedIn Profiles?

Colton Randolph

Subscribe to our newsletter

Get the latest news from Proxycurl

No, we don't scrape contact information from LinkedIn profiles.

However, we integrate our publicly scraped LinkedIn dataset, LinkDB, with other data sources, which allows us to provide a complete enrichment, including contact information.

Meaning we can typically still provide you with contact information for a given LinkedIn, Twitter/X, or Facebook profile while using our API, Proxycurl, despite not scraping contact information from LinkedIn.

For example, it could be as simple as the following cURL query to our Person Profile Endpoint:

curl \
    -G \
    -H "Authorization: Bearer Your_API_Key_Here" \
    '' \
    --data-urlencode 'linkedin_profile_url=' \
    --data-urlencode 'personal_contact_number=include' \
    --data-urlencode 'personal_email=include' \
    --data-urlencode 'use_cache=if-present' \
    --data-urlencode 'fallback_to_cache=on-error'

To enrich a Facebook or Twitter user, you would change this query to use facebook_profile_url or twitter_profile_url instead of linkedin_profile_url. You only need one identifier.

The above cURL query to our Person Profile Endpoint would return you:

  • Profile picture URL: Direct URL to the profile picture.
  • Background cover image URL: Direct URL to the background cover image.
  • First Name, last Name: Name of the individual.
  • Follower count: The number of followers the individual has.
  • Occupation: Current job title and employer.
  • Headline: Professional headline as listed on LinkedIn.
  • Summary: A brief overview of the professional's background, achievements, and goals.
  • Country, city, state: Location details.
  • Company Name: The name of the company where the individual worked.
  • Company LinkedIn profile URL: Direct URL to the company's LinkedIn page.
  • Title: Job title held during the tenure at the company.
  • Description: Description of the role and responsibilities.
  • Start and end dates: The duration of the employment.
  • School Name: The name of the educational institution.
  • School LinkedIn profile URL: Direct URL to the institution's LinkedIn page.
  • Birth date: The birthdate of the user.
  • Degree name and field of study: Specifics of the degree earned.
  • Start and end dates: The duration of the educational program.
  • Languages: Languages spoken by the individual.
  • Certifications: Any certifications that the individual has obtained.
  • Volunteer work: Volunteer positions held, including the organization and the role.
  • Projects: Significant projects that the individual has contributed to, including a description and URL if applicable.
  • Recommendations: Testimonials from colleagues, clients, or employers that underscore the individual's professional capabilities.
  • People also viewed: Other LinkedIn profiles that are frequently viewed alongside this individual's profile.
  • Groups: LinkedIn groups that the individual is a part of, providing insight into their professional interests and affiliations.
  • Interests: A list of interests the user has.
  • Personal emails: A list of personal emails associated with a given identifier.
  • Personal numbers: A list of personal numbers associated with a given identifier.

If you want to return other social media identifiers (such as for messaging), our github_profile_id, facebook_profile_id, and twitter_profile_id parameters will accomplish that with our Person Profile Endpoint.

Please note that any of the above enrichment parameters, including personal_contact_number and personal_email will cost 1 additional credit per successful result returned. For a full breakdown of credit usage costs, view our documentation here.

Finding work email addresses

To enrich a profile with a work email, you'll need to use our Work Email Lookup Endpoint.

The main difference is that it functions via webhooks and a push mechanism. For demonstration purposes, you can use to set up a quick and easy webhook.

Here's how pulling a work email would look via a simple cURL command and a webhook:

curl \
    -G \
    -H "Authorization: Bearer Your_API_Key_Here" \
    '' \
    --data-urlencode 'linkedin_profile_url=' \
    --data-urlencode 'callback_url='

Which returns the following result:

{"email": "[email protected]", "status": "email_found", "profile_url": ""}

More about our Contact API

We also offer our respective Contact API endpoints which may be useful, particularly if you have no interest in general enrichment and only need contact information:

Create your Proxycurl account

Between our Personal Profile Endpoint, including our additional contact enrichment parameters available for it, as well as our Work Email Lookup Endpoint, Personal Email Lookup Endpoint, and Personal Contact Numer Lookup Endpoint, you have several options for contact information enrichment.

If that interests you, you can create your Proxycurl account here. Upon account creation, you'll receive 10 free credits to test out a few queries.

P.S. For more information on our billing policy and pricing, you can review our API pricing page here.

Subscribe to our newsletter

Get the latest news from Proxycurl

Colton Randolph

Featured Articles

Here’s what we’ve been up to recently.