LinkedIn Post Reposts

Paste one or many public LinkedIn post URLs and get every repost as structured data — reposter identity, repost text, content author, timestamps, and a direct-vs-reshare classification. No cookies, no login, no LinkedIn account risk.

Cookieless · Fresh data · No LinkedIn login or account risk.

Watch the demo

Video tutorial coming soon.

What you get

Each dataset item is one unique repost:

• Reposter name, headline, stable ID, public LinkedIn URL, and image URL when available
• Repost activity ID, URL, exact timestamp, and relative time when available
• Text carried by the repost record
• The content author's name, headline, stable ID, LinkedIn URL, and image URL when available
• Original post URL, post ID, and reported repost count
• Explicit direct or reshare classification
• Input and repost indexes for stable multi-post ordering

Results are stored in an Apify dataset and can be exported as JSON, CSV, or Excel. Every output field is scalar, so the records are ready for spreadsheet and CRM workflows as-is.

Direct reposts and reshare-chain rows

• A direct row identifies the reposter directly. The reposter and content author are the same entity in this row.
• A reshare row contains a reshare-chain header. The header identifies the reposter, while the content-author fields identify the actor attached to the available text.

On a reshare row, repost_text can be shared-post text rather than commentary written by the header reposter. Direct rows can omit the repost activity URL, so repost_id, repost_url, and exact timestamps are null when they cannot be established safely.

Output example

{
  "post_url": "https://www.linkedin.com/feed/update/urn:li:activity:7408723748973056001",
  "post_id": "7408723748973056001",
  "post_repost_count": 133,
  "repost_id": "7422118868883513344",
  "repost_url": "https://www.linkedin.com/feed/update/urn:li:activity:7422118868883513344",
  "repost_type": "reshare",
  "repost_action_text": "Example Republisher reposted this",
  "repost_text": "An example of the text available with this repost record.",
  "reposted_at": "2026-01-28T03:30:34.642Z",
  "reposted_at_timestamp": 1769571034642,
  "reposted_at_relative": "6mo",
  "reposter_id": "ACoAAAExampleRepublisherId",
  "reposter_type": "profile",
  "reposter_name": "Example Republisher",
  "reposter_headline": null,
  "reposter_linkedin_url": "https://www.linkedin.com/in/example-republisher",
  "reposter_image_url": null,
  "content_author_id": "ACoAAAExampleContentAuthorId",
  "content_author_type": "profile",
  "content_author_name": "Example Content Author",
  "content_author_headline": "Climate researcher",
  "content_author_linkedin_url": null,
  "content_author_image_url": null,
  "input_index": 0,
  "repost_index": 0,
  "fetched_at": "2026-07-27T13:00:00Z"
}

Input

Field	Type	Required	Default	Description
post_urls	Array of strings	Yes	—	Add 1–1,000 supported public LinkedIn post URLs. Duplicate URLs are normalized and removed while preserving first-seen order.
max_reposts_per_post	Integer	No	100	Maximum deduplicated repost records saved per post. Accepted range: 0–1,000. Use 0 to fetch all available reposts, subject to a 100-page safety cap per post.

Supported URL formats:

https://www.linkedin.com/feed/update/urn:li:activity:7408723748973056001
https://www.linkedin.com/posts/username_topic-activity-7408723748973056001-AbCd
https://www.linkedin.com/posts/username_topic-ugcPost-7408723748973056001-AbCd

Tracking parameters, fragments, and trailing slashes are removed. Bare numeric IDs, profile URLs, company URLs, and search URLs are rejected before any repost request is made.

How to use it

1. Copy one or more supported public LinkedIn post URLs.
2. Paste them into LinkedIn Post URLs.
3. Set Maximum reposts per post, or keep the default of 100.
4. Click Start.
5. Open the dataset to inspect or export the repost records as JSON, CSV, or Excel.

No LinkedIn account, session cookie, browser extension, or proxy configuration is requested in the input form.

Use cases

• Identify people and organizations publicly reposting relevant content
• Research advocates, community members, partners, and potential leads
• Analyze how posts travel through professional networks
• Export reposter identities and repost context into spreadsheets or CRMs
• Build social-listening, content-research, and audience-analysis datasets
• Feed structured repost data into AI, BI, or automation workflows

Pricing

This actor charges per repost result saved (pay-per-event). The current price per result is shown on the actor's Pricing tab — there is no subscription and no minimum. Use max_reposts_per_post to cap exactly how many results a run can produce per post.

Integrations

• API — trigger runs and fetch results programmatically
• Scheduling — monitor posts on a recurring basis
• Webhooks — get notified when a run completes
• Make and Zapier — connect to 1,000+ apps without code
• Google Sheets — pipe results directly into a spreadsheet
• MCP — use this actor as a tool inside Claude, Cursor, or any MCP-compatible AI agent

API example:

curl -X POST \
  "https://api.apify.com/v2/acts/data-slayer~linkedin-post-reposts/runs?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "post_urls": [
      "https://www.linkedin.com/feed/update/urn:li:activity:7408723748973056001"
    ],
    "max_reposts_per_post": 100
  }'

Other LinkedIn Actors by data-slayer

Actor	What it does
LinkedIn Post Performance Scraper	Likes, comments, shares and reaction breakdown for any post
LinkedIn Post Engagers Scraper	Everyone who engaged with a post — commenters, reactors, reposters
LinkedIn Post Comments Scraper	Every comment on a post, with commenter profiles
LinkedIn Post Reactions Scraper	Everyone who reacted to a post, with reactor profiles
LinkedIn Profile Posts Scraper	Recent posts from a profile, with engagement metrics
LinkedIn Profile Scraper	Full profile data from any LinkedIn profile URL
LinkedIn Profile Engagers Scraper	Everyone who engaged across a profile's recent posts, ranked by engagement
LinkedIn Profile Reactions Scraper	Reactions a profile left on other people's posts
LinkedIn Profile Comments Scraper	Comments a profile left on other people's posts
LinkedIn Company Scraper	Full company profile data
LinkedIn Company Posts Scraper	Recent posts from any company page
LinkedIn People Search (ICP)	Find people by title, seniority, function, company, location
LinkedIn Company Search (ICP)	Find companies by industry, size, location and tech stack
LinkedIn Company Employees	Employees at a company, filtered by title, seniority and function
LinkedIn Job Scraper	Full details for LinkedIn job postings
LinkedIn Job Change Tracker	People who recently changed jobs

Which LinkedIn actor should I use?

I have…	And I want…	Use
A post URL	Everyone who reposted	LinkedIn Post Reposts Scraper
A post URL	Everyone who engaged (commenters + reactors + reposters)	LinkedIn Post Engagers Scraper
A post URL	Likes, comments, shares & reaction breakdown	LinkedIn Post Performance Scraper
A post URL	Everyone who commented	LinkedIn Post Comments Scraper
A post URL	Everyone who reacted	LinkedIn Post Reactions Scraper
Profile URL(s)	Their recent posts & engagement	LinkedIn Profile Posts Scraper
A company URL	Recent company posts	LinkedIn Company Posts Scraper

FAQ

Do I need a LinkedIn account, cookie, or login?

No. The input requires supported public LinkedIn post URLs. It does not request your LinkedIn credentials or session cookies.

Are reposts and reshares the same here?

The listing uses both terms because LinkedIn and data tools commonly use them for sharing another post. The repost_type field distinguishes direct rows from later reshare chain rows in the returned source shape.

Why are some repost IDs, URLs, or exact timestamps null?

Direct rows can omit the repost activity URL. Without that URL, the actor does not invent an activity ID or exact timestamp. Relative time can still be available in reposted_at_relative.

Why is a reposter profile URL sometimes null even when reposter_id exists?

Some rows provide an opaque stable profile identifier but no public navigation URL. The actor keeps that identifier in reposter_id and does not treat it as a public profile URL.

Is repost_text always written by reposter_name?

Not on every reshare-chain row. On a direct row, the reposter and content author are the same entity. On a reshare row, the text can belong to content_author_name, while the header reposter is recorded separately.

What does a limit of zero mean?

max_reposts_per_post: 0 requests all available unique reposts, with a maximum of 100 pages per post. Large posts can therefore take longer and consume more usage than a bounded run.

Can I process multiple posts in one run?

Yes. Add up to 1,000 supported post URLs. The runtime processes posts in bounded groups while preserving input-post order in the dataset.

Why can post_repost_count differ from the number of dataset rows?

The reported count describes available reposts at the source. Your configured limit, duplicate removal, page cap, unavailable pages, or source changes can result in fewer saved rows.

Limits and data notes

• Pagination continues automatically until the requested limit, the end of available pages, or the 100-page safety cap.
• max_reposts_per_post is applied after duplicate removal. When a repost ID exists, duplicates keep the first occurrence by post ID plus repost ID.
• Results preserve input-post order and source page order — the actor does not re-sort reposts by timestamp.
• The actor writes a RUN_SUMMARY to the key-value store with per-post status (succeeded, no_results, partial, failed, or capped). If some posts fail, successful rows remain available.
• Works with public posts only. This actor reads only public data and uses no LinkedIn credentials.
• This independent actor is not affiliated with or endorsed by LinkedIn Corporation.

Feedback and support

If a supported public post produces an unexpected result, open an issue from the actor's Issues tab and include the run ID, input URL format, and observed behavior. Do not include credentials or private data.

Related actors

More from the same portfolio. Apify only auto-recommends actors in the same category, so here are the rest of ours:

Actor	What it does
LinkedIn Account Intent Feed	LinkedIn workflow
LinkedIn Buying-Committee Mapper	LinkedIn workflow
LinkedIn Champion Tracker	LinkedIn workflow
LinkedIn Company Employees	LinkedIn workflow
LinkedIn Company Posts Scraper	LinkedIn workflow
LinkedIn Company Scraper	LinkedIn workflow
LinkedIn Company Search (ICP)	LinkedIn workflow
LinkedIn Competitor Content Intelligence	LinkedIn workflow
LinkedIn Competitor Hijack Leads	LinkedIn workflow
LinkedIn Engagement Audience Builder	LinkedIn workflow
LinkedIn Executive Post Monitor	LinkedIn workflow
LinkedIn Hiring Pulse	LinkedIn workflow
LinkedIn Job Change Tracker	LinkedIn workflow
LinkedIn Job Scraper	LinkedIn workflow
LinkedIn Market Map Builder	LinkedIn workflow
LinkedIn People Search (ICP)	LinkedIn workflow
LinkedIn Post Comments	LinkedIn workflow
LinkedIn Post Engagers Scraper	LinkedIn workflow
LinkedIn Post Performance Scraper	LinkedIn workflow
LinkedIn Post Reactions	LinkedIn workflow
LinkedIn Profile Comments	LinkedIn workflow
LinkedIn Profile Engagers Scraper	LinkedIn workflow
LinkedIn Profile Posts Scraper	LinkedIn workflow
LinkedIn Profile Reactions	LinkedIn workflow
LinkedIn Profile Scraper · Fresh · No Cookies	LinkedIn workflow
LinkedIn Skill Mapper	LinkedIn workflow
LinkedIn Talent Flow Mapper	LinkedIn workflow
LinkedIn Talent Mapper	LinkedIn workflow
LinkedIn Warm Path Finder	LinkedIn workflow
LinkedIn Why-Now Account Brief	LinkedIn workflow