LinkedIn Post Reshares & Reposts Scraper - No Cookies

What is LinkedIn Post Reshares & Reposts Scraper?

LinkedIn Post Reshares & Reposts Scraper extracts public reshare/repost data from LinkedIn posts without requiring LinkedIn cookies or a LinkedIn account login. Paste one or more LinkedIn post URLs, click Start, and get a structured dataset with reposter details, repost text, timestamps, engagement metrics, media, and original post context.

Use it to understand who amplified a LinkedIn post, what they said when they reshared it, and which reposts generated engagement. It is useful for B2B marketers, sales teams, recruiters, agencies, analysts, PR teams, and developers who need LinkedIn repost data in CSV, Excel, JSON, or through the Apify API.

What can LinkedIn Post Reshares & Reposts Scraper do?

• Extract public LinkedIn reshares: collect reposts/reshares for a LinkedIn post URL or activity ID.
• Identify people and companies amplifying a post: get reposter names, headlines, profile URLs, and profile images when available.
• Analyze repost commentary: capture the text added by each reposter, including quote-style reposts.
• Measure repost engagement: extract reaction, comment, and share counts where LinkedIn exposes them publicly.
• Keep original post context: include the source post URL, text, author, post type, and media so exports are easy to analyze.
• Process multiple posts in one run: paste a list of LinkedIn post URLs and collect repost data for each one.
• Control pagination and cost: use automatic pagination for convenience or manual page mode when you want precise page-by-page extraction.
• Automate workflows on Apify: schedule runs, monitor results, export datasets, use the API, connect webhooks, and send data to other tools.

What data can you extract?

Data point	Description
Source post URL	The LinkedIn post URL or activity URL used as input.
Source post ID	Normalized LinkedIn post/activity identifier when available.
Source post text	Text from the original post, if publicly available.
Source author	Name, profile/company URL, headline, and image for the original author when available.
Reposter name	Person or company that reshared the post.
Reposter profile URL	LinkedIn profile or company page URL for the reposter.
Reposter headline	Headline, subtitle, role, or company description shown with the repost.
Reposter image	Avatar or company logo URL when available.
Repost text	Commentary added by the reposter. Empty if the post was reshared without commentary.
Repost URL	Direct URL to the repost/reshare when available.
Repost timestamp	Absolute or relative time when the repost was published.
Engagement metrics	Reactions, comments, and share/repost counts where available.
Media	Images, videos, documents, articles, or other media metadata when available.
Page and position	Pagination and ordering metadata for traceability.
Scraped timestamp	Time when the Actor extracted the record.

How to use LinkedIn Post Reshares & Reposts Scraper

1. Open the Actor on Apify.
2. Paste one or more LinkedIn post URLs or activity IDs into LinkedIn post URLs or IDs.
3. Set Maximum reshares per post if you want more or fewer results.
4. Keep Pagination mode set to Automatic unless you want to scrape one specific page.
5. Click Start.
6. Open the Dataset tab to preview results.
7. Export the dataset as JSON, CSV, Excel, XML, or another supported Apify format.

No coding is required for normal use. Developers can run the same scraper with the Apify API, Apify JavaScript client, Apify Python client, schedules, and webhooks.

Input

The main input is a list of LinkedIn post URLs or post IDs. For most users, the default settings are enough: paste the URLs, keep automatic pagination enabled, and choose how many reshares to collect per post.

Input field	Type	Required	Description
postUrls	array	Yes	LinkedIn post URLs, feed update URLs, activity URLs, or supported post/activity IDs.
maxResharesPerPost	integer	No	Maximum number of repost records to save per source post. Default: 100.
paginationMode	string	No	automatic collects pages until the limit is reached. manual collects one page.
pageNumber	integer	No	Page number for manual mode. Ignored in automatic mode.
resultsPerPage	integer	No	Number of results requested per page. Maximum value: 100.
includeOriginalPost	boolean	No	Include original post text, author, URL, and post type.
includeMedia	boolean	No	Include media URLs and metadata when available.
includeEngagement	boolean	No	Include reaction, comment, and share counts when available.
deduplicateResults	boolean	No	Remove duplicate repost records across pages and inputs.
saveErrorsToDataset	boolean	No	Save invalid URL or unavailable post errors as dataset rows.
includeRawData	boolean	No	Include raw source fragments for debugging. This can increase dataset size.
proxyConfiguration	object	No	Proxy settings. Apify Proxy is recommended for reliability.
maxConcurrency	integer	No	Maximum number of concurrent requests. Conservative defaults are recommended.
requestDelayMs	integer	No	Delay between requests in milliseconds. Increase if you see rate limits.
debugLog	boolean	No	Enables verbose troubleshooting logs.

Example input

{
  "postUrls": [
    "https://www.linkedin.com/feed/update/urn:li:activity:7340000000000000000/",
    "https://www.linkedin.com/posts/example_activity-7340000000000000000-abcd"
  ],
  "maxResharesPerPost": 250,
  "paginationMode": "automatic",
  "includeOriginalPost": true,
  "includeMedia": true,
  "includeEngagement": true,
  "deduplicateResults": true
}

Manual pagination example

{
  "postUrls": [
    "https://www.linkedin.com/feed/update/urn:li:activity:7340000000000000000/"
  ],
  "paginationMode": "manual",
  "pageNumber": 2,
  "resultsPerPage": 100
}

Input tips

• Use LinkedIn post URLs, feed update URLs, activity URLs, or supported post IDs.
• Do not use LinkedIn profile URLs, company page URLs, search URLs, or hashtag URLs as source inputs.
• Duplicate URLs are skipped when deduplication is enabled.
• Automatic pagination is easiest for most users.
• Manual pagination is useful when you want page 1, page 2, page 3, and so on as separate runs.
• Higher result limits can increase runtime, proxy usage, and Compute Units.
• Some LinkedIn posts may not expose public reshare data.

Output

Results are saved to the default Apify dataset. Each successful row represents one LinkedIn reshare/repost. You can preview the dataset in Apify Console or export it as JSON, CSV, Excel, XML, HTML, or other supported formats.

For batch runs, every row includes source post fields so you can group results by the original LinkedIn post in spreadsheets, BI tools, CRMs, or custom scripts.

Example output

{
  "recordType": "reshare",
  "sourcePostId": "7340000000000000000",
  "sourcePostUrl": "https://www.linkedin.com/feed/update/urn:li:activity:7340000000000000000/",
  "sourcePostText": "We just published our annual B2B content benchmark report.",
  "sourcePostType": "document",
  "sourceAuthorName": "Example Analytics",
  "sourceAuthorProfileUrl": "https://www.linkedin.com/company/example-analytics/",
  "reshareId": "7351111111111111111",
  "reshareUrl": "https://www.linkedin.com/feed/update/urn:li:activity:7351111111111111111/",
  "reshareText": "Useful benchmark data for anyone planning LinkedIn campaigns this quarter.",
  "reshareType": "quote_repost",
  "resharedAt": "2026-06-16T09:24:00.000Z",
  "resharedAtRelative": "1d",
  "reposterName": "Jane Smith",
  "reposterProfileUrl": "https://www.linkedin.com/in/jane-smith-example/",
  "reposterHeadline": "Demand Generation Manager | B2B SaaS",
  "reposterImageUrl": "https://media.licdn.com/dms/image/example-profile",
  "reposterType": "person",
  "reactionCount": 42,
  "commentCount": 7,
  "shareCount": 3,
  "media": [
    {
      "type": "image",
      "url": "https://media.licdn.com/dms/image/example-image",
      "alt": "Preview image from reshared post"
    }
  ],
  "pageNumber": 1,
  "position": 1,
  "dedupeKey": "7340000000000000000:7351111111111111111",
  "scrapedAt": "2026-06-17T12:00:00.000Z"
}

Error output example

If a URL is invalid or a post is unavailable, the Actor can save an error row instead of silently skipping it.

{
  "recordType": "error",
  "input": "https://www.linkedin.com/in/example-profile/",
  "sourcePostUrl": null,
  "sourcePostId": null,
  "errorCode": "UNSUPPORTED_URL",
  "errorMessage": "The input is a LinkedIn profile URL, not a post URL.",
  "isRetryable": false,
  "pageNumber": null,
  "scrapedAt": "2026-06-17T12:00:00.000Z"
}

How much does it cost to use LinkedIn Post Reshares & Reposts Scraper?

The final Store pricing model should be confirmed by the Actor owner before publishing. Runtime cost depends mainly on:

• Number of LinkedIn posts in the input
• Number of reshares requested per post
• Pagination depth
• Proxy usage
• Whether browser rendering is needed in a future extraction mode
• Memory and concurrency settings
• LinkedIn response speed and availability

Small runs with one post and a low result limit should be cheaper than large batch runs collecting thousands of reshares. For cost control, start with a lower maxResharesPerPost, keep default concurrency, and increase limits only after checking the dataset quality.

Do not assume every post has extractable reshare data. Deleted, private, restricted, or low-engagement posts may return few or no results.

Integrations and API

Because results are stored in Apify datasets, you can use LinkedIn Post Reshares & Reposts Scraper as a no-code tool or as a LinkedIn repost data API.

You can:

• Run the Actor manually in Apify Console.
• Schedule recurring runs to monitor campaign posts.
• Export results to CSV, Excel, JSON, XML, or HTML.
• Connect runs to webhooks.
• Send data to Google Sheets, Make, Zapier, Slack, Airbyte, or your own API.
• Use the Apify API from Node.js, Python, or any HTTP client.

API usage notes

With the Apify API, send the same JSON input shown above. After the run finishes, read the default dataset to get repost records.

Typical automation flow:

1. Start the Actor with post URLs.
2. Wait for run completion or receive a webhook.
3. Fetch dataset items.
4. Send results to your CRM, BI tool, database, or reporting workflow.

Use the official Apify API clients when you want to run the Actor from code. The same input works for a Python LinkedIn scraper workflow, a Node.js LinkedIn scraper workflow, or any HTTP-based automation.

Responsible use and legality

This Actor is intended to extract publicly available LinkedIn post reshare information. It does not require LinkedIn cookies and should not be used to access private, restricted, or login-only content.

You are responsible for using the data lawfully and for complying with LinkedIn's terms, applicable privacy laws, and regulations such as GDPR, CCPA, and other local requirements. Repost data may include personal data such as names, profile URLs, headlines, and profile images. Make sure you have a legitimate reason to process the data and respect deletion, retention, and data-subject rights where applicable.

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation. LinkedIn is a trademark of LinkedIn Corporation. This README is not legal advice.

FAQ

Can I scrape LinkedIn post reshares without cookies?

Yes. This Actor is designed for public LinkedIn post reshare extraction without asking for LinkedIn cookies or account login. Results depend on what LinkedIn exposes publicly for the provided post.

Does it work with any LinkedIn post?

It is intended for public LinkedIn post URLs and activity IDs. It may not work with private posts, deleted posts, restricted posts, posts requiring login, unsupported URL types, or posts where LinkedIn does not expose reshare data.

What is the difference between automatic and manual pagination?

Automatic pagination keeps collecting pages until the Actor reaches maxResharesPerPost or no more results are available. Manual pagination collects only one page, controlled by pageNumber and resultsPerPage.

How many reshares can I extract?

The Actor supports up to the configured maximum per post, with resultsPerPage capped at 100. Very large runs may take longer and cost more. Completeness depends on public availability, pagination behavior, and target-site reliability.

Can I export LinkedIn repost data to CSV or Excel?

Yes. Open the dataset after the run and export results as CSV, Excel, JSON, XML, or other supported Apify dataset formats.

Can I use this as a LinkedIn repost API?

Yes. Run the Actor through the Apify API and read results from the default dataset. This is useful for dashboards, CRM enrichment, campaign reporting, and monitoring workflows.

Does the Actor download images or videos?

By default, it stores media URLs and metadata when available. It does not download large binary media files.

Why are some timestamps relative instead of exact dates?

LinkedIn may expose relative timestamps such as 2h, 1d, or 3w in some views. When an exact timestamp is not reliably available, the Actor preserves the relative value and leaves the absolute timestamp as null.

Why did I get zero results?

Possible reasons include: the post has no public reshares, the post is private or deleted, the URL is unsupported, LinkedIn restricted the data, or the target page changed. Check the dataset for error rows and the run log for warnings.

Troubleshooting

Problem	Possible cause	What to try
No results returned	The post has no public reshares or reshare data is hidden.	Test another public post with known reshares. Lower advanced settings to defaults.
UNSUPPORTED_URL error	Input is not a LinkedIn post/activity URL.	Use a LinkedIn feed update URL, activity URL, post URL, or supported post ID.
Run is slow	High result limit, many posts, proxy latency, or browser rendering.	Reduce maxResharesPerPost, lower batch size, or keep default concurrency.
Rate limiting or blocked requests	Too many requests or proxy/session issue.	Enable Apify Proxy, reduce concurrency, increase requestDelayMs, and retry later.
Missing engagement metrics	LinkedIn did not expose metrics for that repost.	Keep includeEngagement enabled, but expect some fields to be null.
Duplicate-looking rows	Same repost appeared across pages or input URLs.	Keep deduplicateResults enabled. Use dedupeKey for downstream deduplication.
Output has relative timestamps only	Exact timestamp was not available.	Use resharedAtRelative for display and scrapedAt for extraction time context.
Some posts failed in a batch	Individual posts may be invalid, unavailable, or restricted.	Check recordType: "error" rows and rerun only failed valid URLs.

Support and feedback

Use the Issues tab on Apify to report bugs, ask questions, or request features. Include the run ID, input example, expected behavior, and a short description of the problem.

Useful feature requests may include recurring "new reposts only" monitoring, CSV upload, date filtering, minimum engagement filters, CRM integration templates, or deeper profile enrichment through related Actors.