search
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
| URL path segment | Category |
|---|---|
| /results/content/ | posts |
| /results/people/ | people |
| /results/companies/ | companies |
| /results/all/ | people |
| /jobs/search/ | jobs |
Extracted parameters
The following URL query parameters are parsed and mapped to search filters:
- keywords → keywords
- network → connectionDegree (people)
- geoUrn / companyHqGeo → location
- industry → industry
- company / currentCompany → currentCompany
- pastCompany → pastCompany
- school → school
- profileLanguage → profileLanguage
- connectionOf → connectionOf
- firstName / lastName → firstName / lastName
- title → title
- companySize → companySize (companies)
- sortBy → sortBy
- datePosted → datePosted
- f_TPR → datePosted (jobs)
- f_JT → jobType (jobs)
- f_E → experienceLevel (jobs)
- f_WT → workplaceType (jobs)
Pagination override
You can optionally pass start and count to override the pagination embedded in the URL.
Credits
post/search/linkedin/url
Request body
Response
Search results parsed from the LinkedIn URL