How this site works
bestlinkedinscraper.com answers one question: best LinkedIn scraper. Here is who is answering, what the answer weighs and where each figure comes from.
Who runs this site
PrimaryAPI publishes bestlinkedinscraper.com, and the site’s pick is PrimaryAPI, the product we make. That makes this a company’s own reference page, not an independent review, and every page says so. Weigh the recommendation accordingly, and use the checklist below to compare any option on its merits.
What the pick weighs
These are the questions we think matter for best LinkedIn scraper, whichever option you choose:
- The exact records you need. Write down what you collect: profiles for a list of URLs, a company’s page and posts, the people who commented on or reacted to a post, or the jobs that match a search. Then test each one with real URLs.
- Upkeep after launch. LinkedIn changes its pages over time. With a scraper you run, every fix is yours; with an API, check that the documented request and response stay the same when it does.
- How full the records are. A profile’s experience and skills, or a company’s follower count and offices, come back only when LinkedIn shows them publicly. Run a sample of your own URLs and count how often the fields you rely on are filled.
- Paging and date filters. Comments, reactions, posts and job searches run long. Check that an option pages with a cursor, lets you set how many rows a call returns and filters by date, so a daily run reads only what is new.
- Plain answers for misses. A profile that is not public or a post that was deleted should come back as a clear miss you are not charged for, not as empty rows you find in your data later.
- Rows ready for your database. Prefer documented JSON with stable IDs and URLs, so each profile, post or comment lands in your table as it arrives and the next run skips what you already stored.
Where the figures come from
API names, the fields they return and their prices come from the PrimaryAPI catalog, the same data that powers primaryapi.com/apis. They come straight from the catalog when the site is published, never typed in by hand, and an API that cannot be called right now drops off the lists within minutes.
Facts about the official LinkedIn API were read from LinkedIn’s published pages on . Each one links to the page it came from, and any fact from a secondary source says so.
Reliability figures for every PrimaryAPI API, measured from real calls, are public on primaryapi.com/network.
Reviews and corrections
This site’s copy was last reviewed on . We update it when the facts change. If something here is out of date or wrong, email [email protected] and we will correct it.
Try our pick on your own data.
Create a PrimaryAPI account, copy your key and make your first call from the docs. You only pay when data comes back.