Search LinkedIn by URL

Search LinkedIn by URL

Paste any LinkedIn search URL and the endpoint will automatically extract the category, keywords, and all filters from it, then execute the search and return structured results.

When to use this endpoint

• A user gives you a LinkedIn search URL and you want to get the results programmatically
• You want to replicate a search the user performed in their browser
• You want to automate searches based on bookmarked LinkedIn search URLs

Supported URL formats

The endpoint supports all standard LinkedIn search URLs:

• https://www.linkedin.com/search/results/people/?keywords=engineer
• https://www.linkedin.com/search/results/content/?keywords=AI&sortBy=%22date_posted%22
• https://www.linkedin.com/search/results/companies/?keywords=startup&companyHqGeo=%5B%22103644278%22%5D
• https://www.linkedin.com/jobs/search/?keywords=frontend&location=Paris
• https://www.linkedin.com/search/results/all/?keywords=test (treated as people search)

URL path → Category mapping

What is read from the URL

Keywords and every filter the vertical can actually apply, under LinkedIn's own spellings as its filter bar writes them (titleFreeText, schoolFilter, companySizeV2, companyHQBingGeo, industryCompanyVertical) with the bare names accepted as a fallback for a hand-written URL. A company's HEADQUARTERS is kept as its own filter and never folded into the person's location: they are different questions and return different people. Jobs facets are comma-separated in LinkedIn's URLs and each value is read on its own.

A facet the URL carries that this search cannot apply comes back as a URL_FACET entry in warnings, naming the facet. That matters because a dropped filter means the search ran WIDER than the one on the person's screen, so a result set with URL_FACET warnings is a bigger cohort than they asked for and should be described that way.

Pagination override

You can optionally pass start and count to override the pagination embedded in the URL.

Credits