Contact

Scrape LinkedIn profiles

Changed on

Scrape Linkedin profiles by given urls and wait for the result, read the result of a run started earlier (container), or start a run and answer with its id at once (urls with wait: false). The start refuses with a fixed error_code. use_fast_scraper scrapes the urls with the fast scraper in either mode. A waiting fast scrape of several urls, or a waiting read of a fast-scraper run, waits up to 30 seconds for the emails and the merge, then answers 202 with the run's id and status processing.

post/api/contacts/linkedin/scraping

Request

Request body

urlsstring[] required
containerstring

Read the result of a run started earlier, instead of scraping urls.

waitboolean

false answers at once instead of waiting. With urls: starts the run and answers 202 with its id. With container: answers 202 with status running (PhantomBuster is still scraping) or processing (the emails are still being found), then 200 with the profiles once ready; the result stays readable for 7 days.

use_fast_scraperboolean

Scrape the urls with the fast scraper, in either wait mode. Its profiles are merged into the stored ones, and a profile only the fast scraper ever read has no phone, other social links or jobs before the previous one. A container read finds out from the container which scraper ran it, so it needs no flag.

Response

Success

namestring required
positionstring required
company_namestring
company_urlstring
profile_picturestring required
locationstring required
linkedinstring required
twitterstring required
work_phonestring required
emailstring required
email_statusstring required
linkedin_datastring[] required

Data fetched from Linkedin, with jobs, schools, skills, general data etc.

Example response

{
  "name": "John Doe",
  "position": "Software Engineer",
  "company_name": "Company Inc.",
  "company_url": "https://company.com",
  "profile_picture": "https://image.com/johndoe.jpg",
  "location": "New York, USA",
  "linkedin": "https://www.linkedin.com/in/johndoe/",
  "twitter": "https://twitter.com/johndoe/",
  "work_phone": "+1234567890",
  "email": "john.doe@email.com",
  "email_status": "valid",
  "current_jobs": [
    {
      "companyUrl": "https://www.linkedin.com/company/123456/",
      "companyName": "Company Inc.",
      "logoUrl": "https://image.com/company.jpg",
      "jobTitle": "Software Engineer",
      "dateRange": "Aug 2022 - Present",
      "startedSince": "2022-08-01",
      "isCurrent": true,
      "duration": "1 yr 8 mos",
      "location": "New York, USA"
    }
  ]
}

Changes

    • breaking

      added subschema #3 to the response body oneOf list for the response status

    • info

      added the new optional request property