LinkedIn scraper and API skills
Site: linkedin.com
LinkedIn's APIs are partner-gated and job search is not exposed at any tier. These LinkedIn scraper skills read the public guest jobs endpoint through the Browserless MCP — no cookies, no auth, no residential proxy — and return structured JSON.
Working with LinkedIn
- The guest jobs endpoint is the optimal surface: a single goto plus evaluate, with no cookies, User-Agent spoofing or proxy needed.
- sortBy=DD is what produces descending-date ordering; without it results are relevance-ranked.
1 LinkedIn skill
LinkedIn scraping questions
- Does LinkedIn have an API?
- No usable one. The Marketing and Talent APIs require an approved partnership, and job search is not part of either.
- Is scraping LinkedIn legal?
- Reading data that LinkedIn publishes publicly is generally treated as lawful in the US — hiQ v. LinkedIn found that scraping a public site does not by itself violate the Computer Fraud and Abuse Act. That is not the whole question: LinkedIn's terms of service, its robots.txt, the rate at which you request pages, and any personal or copyrighted data you collect all carry their own obligations, and the rules differ outside the US. These skills read public pages at human-scale rates and never bypass a login. Treat this as background, not legal advice.
- What data can I extract from LinkedIn?
- Job title, company, location, posting URL and posted-date ordering, taken from the public guest jobs endpoint.