No, we don't scrape contact information from professional networks profiles.
However, we integrate our publicly scraped profile 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 the platform, Twitter/X, or Facebook profile while using our API, Enrich Layer, despite not scraping contact information from professional networking platforms.
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" \ ' platform' \ --data-urlencode 'linkedin_profile_ \ --data-urlencode 'personal_contact_ \ --data-urlencode 'personal_ \ --data-urlencode 'use_ \ --data-urlencode 'fallback_to_
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 the platform. -
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 professional networks profile URL: Direct URL to the company's the platform 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 professional networks profile URL: Direct URL to the institution's the platform page.