LinkedIn Post Scraper

💼 LinkedIn Post Scraper

Collect public LinkedIn posts from company pages, personal profiles, or single post links: text, author, reactions, comments, and publish time. No login, no cookies, no LinkedIn account at risk. $0.001 per post, which is $1 per 1,000.

✨ Why use LinkedIn Post Scraper?

• 🔓 No login needed — reads the public LinkedIn pages that anyone can open, so no session cookie to manage.
• 🏢 Companies, people, and single posts — paste a company page, a profile, or a direct post link.
• 📊 Engagement counts — reactions and comment counts on every post, plus up to 10 embedded comments when the page shows them.
• 🕒 Exact timing — an ISO publish time from the post page, alongside the relative age.
• 📅 Date filter — keep only posts after a date.
• 💸 Very cheap — a flat $1 per 1,000 posts.

🎯 Use cases

• 🕵️ Competitor monitoring — follow what rival companies announce and how audiences react.
• 📈 Content research — see which topics earn reactions on company and executive pages.
• 🤝 Sales intelligence — track posts from target accounts and decision makers.
• 🗞️ PR and brand tracking — log executive and company posts over time.
• 🧪 Datasets — build corpora of public business posts for analysis.

🚀 How to use

1. Paste LinkedIn URLs into LinkedIn URLs, one per line: a company page, a profile, or a post link.
2. Set Posts per URL (default 10).
3. Optionally set Only posts after to skip older posts.
4. Click Start.
5. Export the results as JSON, CSV, or Excel, or fetch them through the API.

📥 Input

{
  "urls": [
    "https://www.linkedin.com/company/microsoft",
    "https://www.linkedin.com/in/satyanadella"
  ],
  "limitPerSource": 10,
  "proxyConfiguration": {
    "useScrapelyProxy": true,
    "scrapelyProxyGroups": ["DATACENTER"]
  }
}

📤 Output

One row per post.

Example item (trimmed):

{
  "urn": "urn:li:activity:7514395953961881600",
  "url": "https://www.linkedin.com/posts/microsoft_activity-7514395953961881600-h6eR",
  "inputUrl": "https://www.linkedin.com/company/microsoft",
  "text": "Introducing Microsoft-Decision-1, our new model for fast decision-making. ...",
  "timeSincePosted": "4d",
  "postedAtISO": "2026-10-09T18:46:46.143Z",
  "numLikes": 9272,
  "numComments": 401,
  "authorName": "Satya Nadella",
  "authorProfileUrl": "https://www.linkedin.com/in/satyanadella",
  "authorType": "Person",
  "comments": [
    {
      "text": "Satya, how do you share deep, technical industry expertise without making your posts too boring ...",
      "postedAtISO": "2026-10-09T19:08:43.654Z",
      "authorName": null
    }
  ]
}

💰 Pricing

$0.001 per post ($1 per 1,000 posts). Platform usage is billed on top at standard rates (compute $0.30 per GB-hour, datacenter proxy $1 per GB).

Worked example: a company feed of 10 posts costs 10 × $0.001 = $0.01 in post fees. With platform usage, our measured cost for that job was about $0.013.

❓ FAQ

Is it legal to scrape LinkedIn posts?

The actor reads only public pages that LinkedIn shows without logging in. You are responsible for following LinkedIn's terms and privacy laws such as GDPR.

Do I need a LinkedIn account or cookies?

No. There is no login at all.

How many posts can I get per URL?

As many as the public page shows. Public company and profile pages usually show about 10, so expect around that.

What if a field is empty?

Share counts, impressions, and member ids are not on the public page, so those fields are null.

Can I schedule it or use the API?

Yes. Use Schedules for regular runs, or start the actor over the REST API and read the dataset in JSON, CSV, or Excel.

⚠️ Limits

• No keyword or hashtag search. LinkedIn sends logged-out search to its login page, so search URLs are skipped.
• Public pages show about 10 recent posts per company or profile.
• Share counts, impressions, member URNs, and lists of who reacted are not available.
• Embedded comments are limited to the ones shown on the public post page (up to 10).
• Long company runs can be slower on some days, since LinkedIn response time varies. In testing, 110 company pages (about 930 posts) took about 5.5 minutes.
• Very long URL lists (roughly 150 or more) can exceed the run input size limit; split them into several runs.