LinkedIn Post Search Scraper

Search public LinkedIn posts, feed updates, and Pulse articles by keyword and export structured post data to JSON, CSV, Excel, or the Apify API.

This actor is built for social listening, B2B market research, GTM teams, founders, investors, analysts, and AI agents that need a clean feed of public LinkedIn discussions around a topic, company, competitor, product category, or phrase.

The actor uses ScrapeCreators' public LinkedIn post search endpoint. That endpoint finds Google-indexed public LinkedIn posts and then extracts the visible LinkedIn page details. It does not use LinkedIn login cookies, does not access private posts, and does not claim complete LinkedIn-native search coverage.

What It Extracts

Each dataset item represents one public LinkedIn post or article.

Field	Description
postUrl	Public LinkedIn post, feed update, or article URL
postId	LinkedIn activity or article ID parsed from the URL when available
publishedAt	Publication timestamp when LinkedIn exposes it publicly
description	Public post text or article description
authorName	Public author name
authorUrl	Public LinkedIn author profile or page URL
authorFollowers	Follower count when available
likeCount	Public like/reaction count when available
commentCount	Public comment count when available
engagementCount	likeCount + commentCount when at least one count is available
mediaUrl / imageUrl	Media URLs exposed on the public page
comments	Public comments returned by the provider when enabled
runId	Apify run ID that produced the record
searchQuery	Input query used for this record
source	Data provider used
scrapedAt	Timestamp when this actor saved the record

Inputs

• query - keyword or phrase to search for.
• datePosted - optional freshness filter: any time, last hour, last day, last week, last month, or last year.
• maxResults - hard cap on saved posts and billed post events.
• maxProviderPages - advanced pagination safety cap. Keep the default unless you intentionally want to limit upstream calls.
• startCursor - continue from a previous run's nextCursor.
• includeComments - include public comments returned with each post.
• outputMode - full for all supported fields, compact for smaller LLM-friendly records.

Example Input

{
  "query": "ai agents",
  "datePosted": "last-week",
  "maxResults": 50,
  "maxProviderPages": 60,
  "includeComments": true,
  "outputMode": "full"
}

Example Output

{
  "postUrl": "https://www.linkedin.com/posts/aagupta_what-you-need-to-know-ai-agents-activity-7354600338621906944-RvXR",
  "postId": "7354600338621906944",
  "searchQuery": "ai agents",
  "datePosted": "last-week",
  "publishedAt": "2025-07-25T19:56:02.566Z",
  "description": "There's way too much hype about AI agents...",
  "authorName": "Aakash Gupta",
  "authorUrl": "https://www.linkedin.com/in/aagupta",
  "authorFollowers": 313422,
  "likeCount": 217,
  "commentCount": 25,
  "engagementCount": 242,
  "position": 1,
  "runId": "6neqzJ0WbGrfDOHb4",
  "source": "scrapecreators",
  "scrapedAt": "2026-06-08T00:00:00.000Z"
}

Run Summary and Cursors

Every run writes a machine-readable OUTPUT record to the default key-value store. Use it to decide what to do next:

{
  "savedCount": 50,
  "chargedThisRun": 50,
  "estimatedPpeCostUsd": 0.25,
  "pagesFetched": 4,
  "nextCursor": "5",
  "stopReason": "max-results-reached",
  "providerAttempts": 4,
  "providerRetries": 0,
  "providerStatusCodes": [200]
}

To continue, pass nextCursor from the previous OUTPUT as startCursor in the next run. Common stopReason values are:

• max-results-reached - the actor reached your maxResults cap.
• no-results - the provider found no public indexed posts for the query and date filter.
• no-more-results - the provider page had no additional cursor.
• max-provider-pages-reached - the advanced page safety cap stopped pagination.
• provider-error or partial-provider-error - upstream provider failed before or after some records were saved.

Use Cases

• Monitor public LinkedIn conversations about your company, competitors, or category.
• Find high-engagement posts about emerging B2B topics.
• Build lead and account research workflows around public market signals.
• Feed AI agents with recent public LinkedIn discussions for summarization and trend analysis.
• Track thought leaders and public reactions around launches, funding news, product categories, or conferences.

Pricing

This actor is designed for pay-per-event monetization:

• apify-actor-start: platform start event.
• post-found: one public LinkedIn post saved to the dataset.

The actor logs the maximum possible post-event cost before it starts and stops before saving or charging more than maxResults.

The default run memory is 512 MB because this is an API-backed actor, not a browser crawler. That keeps the platform start event lighter while still leaving enough room for large JSON pages.

Limitations

LinkedIn post search is best-effort. Results depend on what Google has indexed and what LinkedIn exposes publicly. This actor does not scrape private LinkedIn content, does not use account cookies, and does not provide a complete LinkedIn-native search index.

For known post URLs, use a LinkedIn post-detail scraper. For LinkedIn jobs or profile emails, use actors built specifically for those data types.

API Example

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~linkedin-post-search-scraper/runs?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"query":"ai agents","datePosted":"last-week","maxResults":25}'

Legal

This actor is intended for public web data that is visible without authentication. You are responsible for using the output in compliance with applicable laws, platform terms, privacy requirements, and your own data governance policies.