Contact
Scrape LinkedIn profiles
Changed onScrape 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
- Base URLhttps://api.sponsorunited.com (the document declares no server; this is the origin it was published from)
- AuthHTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Request body
Response
Success
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 #3to the response bodyoneOflist for the response status - info
added the new optional request property
- breaking