📝 LinkedIn Posts API | Scrape Profile Posts & Engagement

The LinkedIn Posts API turns public LinkedIn posts into clean, structured JSON. Use this actor with Claude, Cursor, or any MCP-compatible AI agent to collect post text, reactions, comments, media, hashtags, and author details from LinkedIn's public pages, billed per post.

Give it a person or company URL and it returns the recent posts LinkedIn shows publicly, or give it specific post URLs to fetch directly. It works as a straightforward LinkedIn posts scraper for content research, post engagement analysis, and social listening, and it is built API-first and MCP-ready so AI agents can call it as a tool.

---

🧩 Part of the Alpha OSINT LinkedIn suite: no login, no cookies

Eight Actors that read only what LinkedIn shows to a signed-out visitor. None of them asks for your account, your password or an li_at session cookie, so none of them can get your LinkedIn account restricted. Each one takes what the previous one returns, so you can chain them into a full people-and-company workflow:

Step	You want to	Use
1	Find people by name, job title, company, school or location, no profile URL needed	LinkedIn People Search API
2	Turn profile URLs into full structured profiles: experience, education, followers	LinkedIn Profile API
3	Enrich the employer: industry, size, headquarters, specialties, follower count	LinkedIn Company API
4	List the people who work at a company, each checked against their public profile	LinkedIn Company Employees API
5	See what a company is hiring for, with salary data where LinkedIn publishes it	LinkedIn Jobs API
6	Search jobs as a guest with filters, total result counts and autocomplete ids	LinkedIn Job Scraper
7	Read what a person or company posts, with reactions and comments	LinkedIn Posts API (this Actor)
8	Map the skills people list to courses, learner reviews and full syllabi	LinkedIn Learning API

A worked map of these chains, with live adoption and success-rate stats for every Actor, is at alphaosint.com/linkedin.

📋 What this API returns

Field	Description
postUrl, postId	The post's public URL and identifier.
postType	The kind of post: post, repost (quotes or reshares another post), video, document, or article.
datePosted	When the post was published, as an exact ISO 8601 timestamp.
title, text	The post title (for articles) and body text.
hashtags	Hashtags used in the post.
authorName, authorHeadline, authorUrl	Who posted it (display name), their headline and profile URL.
authorFollowers, authorType	Author audience size and person/company type.
numLikes, numComments	Engagement counts.
images, videos, embeddedLinks	Media and links attached to the post.
taggedCompanies, taggedPeople	Entities tagged in the post.
topComments	A sample of the most visible comments.
resharedPost, document	The post it quotes or reshares, and any document or carousel attached.
isRepost, isInfluencer	Company feeds: whether the company reposted someone else's post; whether LinkedIn marks the author as an Influencer.
fromCache	True when the row came from the shared cache (see below).
summary	A plain-language one-line interpretation of the post.

Sources and limits

Everything comes from LinkedIn's public pages, the ones a signed-out visitor sees:

• Post URLs: the post's own public page. Full text, reactions, comments shown to visitors, mentions, images, video and documents.
• Person profile URLs: the recent posts the public profile shows, usually 3 to 8. That is all LinkedIn shows a signed-out visitor, so a profile can return fewer posts than maxPostsPerProfile.
• Company page URLs: the company's public feed, newest first, up to about 70 recent updates.

Not available: share and repost counts (numShares), which LinkedIn does not show signed-out visitors. Dates are exact, read from the post's own id.

---

🎯 Use cases

• Content research. Pull a creator's or brand's recent posts to study what performs.
• Competitive monitoring. Track a competitor's LinkedIn posts and engagement over time.
• Social listening. Collect posts and their reactions and comments for sentiment and trend analysis.
• Lead generation. Find the most-engaged posts from target accounts to spot warm prospects.
• Personal brand analytics. Measure reactions and comments across your own posts.
• AI agent workflows. Drive this API over MCP from Claude to fetch and summarize posts in-conversation.

---

🔁 Use it as a LinkedIn posts scraper at scale

Point this LinkedIn posts scraper at a profile or a company page and it returns their recent posts, one clean row each, with the same flat fields every time, which is what makes the output easy to load into a sheet, a database, or a BI tool. Cap each profile with maxPostsPerProfile so a large run never overshoots your budget, and narrow discovery with startDate and endDate to a specific window.

Every row carries the post engagement you care about: reactions and comments, alongside the post text, hashtags, and author details. That makes it a ready source for content research, tracking a creator or brand, and finding the highest-engagement influencer posts. If a profile has no public posts, you get a clear error row instead of a failed run, so one empty profile never sinks the batch.

---

⚙️ Input examples

Discover a profile's posts

{
  "profileUrls": ["https://www.linkedin.com/in/williamhgates"],
  "maxPostsPerProfile": 20
}

Limit discovery to a date range

{
  "profileUrls": ["https://www.linkedin.com/in/williamhgates"],
  "maxPostsPerProfile": 50,
  "startDate": "2025-01-01",
  "endDate": "2025-12-31"
}

Read a company's feed

{
  "profileUrls": ["https://www.linkedin.com/company/apify"],
  "maxPostsPerProfile": 50,
  "includeReposts": false
}

Fetch specific posts by URL

{
  "postUrls": [
    "https://www.linkedin.com/posts/williamhgates_activity-7446904645010210816"
  ]
}

maxPostsPerProfile caps how many posts are returned per profile, so you control cost. The API returns one row per post. Set includeReposts to also get posts a company reposted from other authors.

Freshness and the shared cache

Recently fetched posts are kept in a shared cache for a short time: posts for up to 3 days, company feed pages for up to 6 hours. A request inside that window is served from the cache, and the row says "fromCache": true with fetched_at set to the original fetch time. Set maxAgeDays to accept only results fetched within that many days, or 0 to always fetch fresh. To have a cached post removed, open an issue.

---

📤 Example output

Each post is returned as one JSON row:

{
  "result_type": "post",
  "postId": "7446904645010210816",
  "postUrl": "https://www.linkedin.com/posts/williamhgates_activity-7446904645010210816",
  "postType": "post",
  "datePosted": "2025-06-01T12:00:00.000Z",
  "text": "A few books shaped how I think about clean energy this year...",
  "hashtags": ["#cleanenergy", "#books"],
  "authorName": "Bill Gates",
  "authorHeadline": "Chair, Gates Foundation and Founder, Breakthrough Energy",
  "authorUrl": "https://www.linkedin.com/in/williamhgates",
  "authorType": "Person",
  "numLikes": 12045,
  "numComments": 843,
  "videos": [],
  "fromCache": false,
  "summary": "Post by Bill Gates, 12,045 reactions, 843 comments, posted 2025-06-01"
}

---

💰 Pricing (pay-per-event)

You pay per post returned. There is no per-run setup fee. The current per-event price is shown on the Store card and in the Actor's Monetization details. Because billing is per post, you only pay for the posts actually delivered, and maxPostsPerProfile lets you cap the volume of each run.

---

🔌 Use the LinkedIn Posts API from Claude (MCP)

This Actor is MCP-server-compatible, so Claude Code (free trial), Claude (desktop and web), Cursor, and other MCP clients can call it as a tool through Apify's hosted MCP server.

Add it with this Actor-specific URL:

https://mcp.apify.com/?tools=actors,docs,johnvc/linkedin-posts-api

Apify MCP integration docs: https://docs.apify.com/platform/integrations/mcp

Setup walkthrough:

New to Claude Code or Claude Cowork? Start a free trial.

Then ask Claude:

"Use the LinkedIn Posts API to pull Bill Gates's last 10 posts and summarize which got the most engagement."

---

💸 Pay per run with crypto (x402)

The LinkedIn Posts API supports agentic payments via the x402 protocol. AI agents and MCP clients can pay for runs in USDC (on Base) with no Apify account or API token needed: point your agent at the Apify MCP server and it can discover, pay for, and run this Actor autonomously. Read the Apify x402 announcement for details.

🔌 Integrations: track post engagement on a schedule

This API earns its keep as a recurring step in a pipeline, not a one-off run:

• Tasks and Schedules. Save a set of profile URLs as a Task, then attach a Schedule to pull new posts and their engagement daily, weekly, or monthly with no code.
• n8n, Make, and Zapier. Trigger a run on a schedule, then route new posts into a content dashboard, a Slack channel, or your CRM. Apify has native connectors for each.
• Supabase, Google Sheets, and databases. Send the dataset straight to storage with a webhook or the Apify API so the rows land where your team already works.
• MCP. Call the API as a tool from Claude and other AI agents (see the section above) to fetch and summarize posts inside an agent workflow.
• Webhooks. Fire a webhook on run completion to kick off the next step in your own system, such as scoring the most-engaged posts.

---

🔗 Related Tools

Build a full picture of a person, their posts, and where they work by pairing this with the rest of the LinkedIn suite:

• LinkedIn Profile API - structured profile data on the people whose posts you collect.
• LinkedIn Company API - firmographics for the companies behind the authors.
• LinkedIn Jobs API - open roles by keyword and location, a companion hiring signal.
• LinkedIn Learning API - public course data, ratings and syllabus for the topics an author posts about.
• YouTube Download API: archive the YouTube videos that the creators you track share in their posts.

Comparison point: many LinkedIn posts tools on the Store cover only one slice of engagement (for example harvestapi/linkedin-post-reactions, reactions only). This API returns the full post, text, reactions, and comments, in one row, with pay-per-post billing and MCP access from AI agents.

---

📎 Applications

Ready-made task pages for common jobs. Open one, run it, or duplicate it as a starting point:

Scrape LinkedIn Posts to Structured JSON

Turn a profile URL into clean JSON: post text, reactions, comments, date, and author, newest first.

Track a Profile's LinkedIn Posts

Pull a profile's recent posts on a schedule, filtered to a date range.

Analyze LinkedIn Post Engagement

Get reactions, comments, author, and follower count per post, ready for a dashboard.

Collect Influencer Posts from LinkedIn

Pull a creator's recent posts with reach and engagement for influencer research.

LinkedIn Posts Data API for Python

Call the API from Python: a profile URL in, structured posts out.

Scrape LinkedIn Posts in an n8n Workflow

Add post data to an n8n workflow: pass profile URLs, get structured rows back.

Get LinkedIn Posts in Claude via MCP

Use posts as a tool in Claude and other AI agents over MCP.

Fetch Specific LinkedIn Posts by URL

Paste up to 1000 post URLs and get one clean row each.

---

🚀 How to get started

1. Open the Actor and paste one or more LinkedIn profile or company URLs into profileUrls (or post URLs into postUrls).
2. Set maxPostsPerProfile to bound the volume, then run it and read the results from the dataset (JSON, CSV, Excel, or API).

View on Apify Store

Example code: Python quick-start + MCP setup on GitHub - call the API from Python, or install it as a tool in Claude, Cursor, and ChatGPT.

---

🤖 Ask an AI assistant about this API

Open a ready-to-send prompt about the LinkedIn Posts API in the AI of your choice:

• 💬 ChatGPT
• 🧠 Claude
• 🔍 Perplexity
• 🅒 Copilot

❓ FAQ

Do I need to give you my LinkedIn cookies or login?

No, never. This Actor does not ask for, accept or store your LinkedIn cookies, your session cookie (li_at), your password or your account. There is no input field for any of them. It reads LinkedIn's public pages the way a signed-out visitor sees them. Any cookie involved is one LinkedIn's site hands to that anonymous visit, and it is used only inside that single run.

Is this a LinkedIn Posts API or a LinkedIn posts scraper?

Both descriptions fit. You call it like an API (a profile or post URL in, structured JSON out), and under the hood it is a LinkedIn posts scraper that reads LinkedIn's public pages. You never touch scraping infrastructure; you get clean, one-row-per-post data back.

What input should I provide?

A public LinkedIn profile URL (e.g. https://www.linkedin.com/in/williamhgates) or company URL (e.g. https://www.linkedin.com/company/apify) to discover its posts, and/or specific post URLs to fetch directly. Supply at least one.

How many posts do I get per profile?

Up to maxPostsPerProfile (default 20, up to 200), limited by what LinkedIn shows a signed-out visitor: a person's public profile shows only their few most recent posts (usually 3 to 8), and a company feed goes back about 70 updates. Newest posts are returned first, and you can narrow the range with startDate and endDate.

Do you return comment and reaction counts?

Yes. Each post row includes reaction and comment counts, plus a sample of the most visible comments, so the output doubles as post engagement data. Share counts are not shown on LinkedIn's public pages, so they are not included.

Is it legal to scrape public LinkedIn posts?

This actor collects only public post data. Public-data scraping has been addressed in court cases such as hiQ Labs v. LinkedIn, but you are responsible for your own use, including GDPR and platform terms. Consult your own counsel for your use case.

Can I run it from Claude or another AI agent over MCP?

Yes. The Actor is MCP-server-compatible, so Claude Code (free trial) and other MCP clients call it as a tool. See the MCP section above for the setup URL.

Can I schedule it or connect it to my other apps?

Yes. Save your profile URLs as a Task and attach a Schedule for recurring runs, and connect the output to n8n, Make, Zapier, Supabase, or your own system by webhook. See the Integrations section above.

What if a profile has no public posts?

The API returns a clear error row for that profile explaining why, so one empty profile does not fail the whole run.

---

🌐 About Alpha OSINT

This Actor is part of Alpha OSINT, toolset of financial and operations data sources and APIs. See the LinkedIn Posts API source page for related tools and use cases. For support or requests for this actor, please start a ticket directly on our support page.

Last Updated: 2026.10.04