LinkedIn job scraping
LinkedIn is the second verified source in the Group Oject multi-board Actor. Public job collection does not require a LinkedIn login. This does not guarantee that every query, country or full description will be available.
Ready-to-run input
Use this configuration in the Actor’s JSON input. Review the live price and set a maximum run charge before starting. Limits are maximums, not guaranteed output counts.
{
"searchTerm": "software engineer",
"location": "New York, NY",
"jobBoards": [
"linkedin"
],
"countryIndeed": "USA",
"maxResultsPerSite": 20,
"maxItems": 20
}Choose a small comparison
Run the same role and city against Indeed and LinkedIn. Inspect each source separately before assuming the combined dataset represents the whole hiring market. Job-board search order matters when the combined output cap is reached.
Handle duplicate postings
The Actor deduplicates normalized listing URLs and shared direct-application URLs when available. Two jobs with similar titles are not necessarily the same requisition. Keep source metadata when analyzing overlap.
Treat descriptions and salaries as optional
Full LinkedIn descriptions can be requested where supported, but availability depends on the source response. Do not interpret a missing salary as zero or invent contact details.
Separate core and beta sources
Indeed is the default and LinkedIn is a verified second source. Google Jobs, Glassdoor, ZipRecruiter, Bayt and Naukri remain beta. Adding more boards can increase latency without increasing useful output.
Sources & next step
This guide describes the Group Oject Actor. Consult its current input schema, README and pricing before running. For integration details, see the Apify API documentation.
Build your searchRun on Apify