LinkedIn Post Search Scraper avatar

LinkedIn Post Search Scraper

Pricing

from $3.00 / 1,000 results

Go to Apify Store
LinkedIn Post Search Scraper

LinkedIn Post Search Scraper

Search LinkedIn for posts by keyword, topic, or hashtag. Filter by date posted and sort by relevance or recency.

Pricing

from $3.00 / 1,000 results

Rating

0.0

(0)

Developer

Crawler Bros

Crawler Bros

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

19 hours ago

Last modified

Share

Search LinkedIn for posts by keyword, topic, or hashtag using the LinkedIn Voyager API (HTTP-only — no browser required). Returns matching posts with full content, author details, and engagement metrics. Supports filtering by date posted and sorting by relevance or recency.


What It Does

  • Searches LinkedIn posts using any keyword, phrase, or hashtag
  • Returns post content, author name, headline, profile URL, and post URL
  • Includes engagement metrics: reactions count and comments count
  • Filters by date posted: past 24 hours, past week, past month, or any time
  • Sorts by most relevant or most recent
  • Deduplicates results automatically
  • Requires a valid LinkedIn session cookie (li_at)

Input

FieldTypeRequiredDescription
searchQueryStringYesKeywords, phrase, or hashtag to search. E.g. artificial intelligence, #MachineLearning, product launch
cookieStringYesLinkedIn session cookie. Accepts plain li_at value or full browser cookies JSON array
sortBySelectNorelevance (default) or recency
datePostedSelectNo"" Any time (default), r86400 Past 24h, r604800 Past week, r2592000 Past month
maxResultsIntegerNoMax posts to return. Default: 25, max: 100
proxyConfigurationObjectNoApify proxy configuration. Defaults to residential then datacenter AUTO

Output

Each item in the dataset represents one LinkedIn post:

FieldTypeDescription
postIdStringNumeric LinkedIn activity ID
postUrlStringDirect URL to the post
authorNameStringDisplay name of the post author
authorProfileUrlStringAuthor's LinkedIn profile URL
authorHeadlineStringAuthor's headline (job title, company, location)
postedAtStringWhen the post was published (e.g. "1 day ago", "2 weeks ago")
contentStringPost text content (may be truncated for long posts)
mediaTypeStringAlways text for search results (detailed media info not available via search API)
reactionsCountIntegerNumber of reactions on the post
commentsCountIntegerNumber of comments on the post
scrapedAtStringISO 8601 UTC timestamp when the record was collected

Example Output

{
"postId": "7329761432933134337",
"postUrl": "https://www.linkedin.com/feed/update/urn:li:activity:7329761432933134337/",
"authorName": "Jane Doe",
"authorProfileUrl": "https://www.linkedin.com/in/janedoe/",
"authorHeadline": "Senior AI Engineer at Acme Corp | San Francisco",
"postedAt": "1 day ago",
"content": "Excited to share that we just launched our new AI-powered product! After 18 months of development...",
"mediaType": "text",
"reactionsCount": 347,
"commentsCount": 42,
"scrapedAt": "2026-06-08T12:34:56.789000+00:00"
}

LinkedIn requires authentication to access search results. You need to provide your li_at session cookie.

Option 1: Plain li_at value (simplest)

  1. Open linkedin.com in your browser and log in
  2. Open DevTools (F12 or right-click → Inspect)
  3. Go to ApplicationCookieshttps://www.linkedin.com
  4. Find the cookie named li_at
  5. Copy the Value and paste it into the cookie input field

Option 2: Full browser cookies JSON array

  1. Install a browser extension like EditThisCookie or Cookie-Editor
  2. Log into LinkedIn
  3. Export all cookies as JSON from the extension
  4. Paste the full JSON array into the cookie input field

Note: Your cookie is used only for authentication with LinkedIn's API. Never share it publicly. Cookies typically expire after 1 year or when you log out of LinkedIn.


Search TypeExample InputWhat It Finds
Keyword phraseartificial intelligencePosts mentioning the exact phrase or related terms
Single keywordstartupPosts containing the word startup
Hashtag#MachineLearningPosts tagged with that hashtag
Multi-wordproduct launch announcementPosts about product launches
Person mentionElon Musk TeslaPosts mentioning Elon Musk in context of Tesla

Sort and Filter Combinations

sortBydatePostedWhat You Get
relevance(empty)Most relevant posts of all time
relevancer86400Most relevant posts from last 24 hours
recency(empty)Newest posts first, no date filter
recencyr86400Most recent posts from last 24 hours
recencyr604800Most recent posts from last week
recencyr2592000Most recent posts from last month

FAQs

How many posts can I scrape per run? Up to 100 posts per run (set via maxResults). LinkedIn's search API returns results in pages of 10.

Why are some engagement counts zero? LinkedIn's search API does not always return engagement data in search result previews. When the socialProofText field is absent from the result, counts default to 0. Use the LinkedIn Post Scraper actor to get full engagement data for specific posts.

Why is post content sometimes truncated? Search results return a content snippet, not the full post text. Long posts are cut off by LinkedIn's search API. To retrieve the full text, visit the post URL directly.

What causes rate limiting? LinkedIn throttles search requests. The actor automatically adds delays between requests (2–5 seconds) and retries on 429 responses. If you need to scrape large volumes, increase the delay by reducing maxResults and running multiple actors.

Do I need a proxy? A proxy is recommended but not required. The actor first tries a residential proxy (best for LinkedIn), then falls back to datacenter proxy, then direct connection. You can also supply a custom proxyConfiguration.

Why does the actor fail with "cookie is invalid or expired"? Your li_at cookie has expired or LinkedIn invalidated the session. Log out and back into LinkedIn, then copy the fresh li_at value.

Can I search posts in other languages? Yes. Enter your search query in any language. LinkedIn returns results in the language of the posts matching your query.

Is logging in or a paid LinkedIn account required? No paid subscription is required. Any standard LinkedIn account works. The li_at session cookie from a free account is sufficient.

Explore the rest of the LinkedIn suite

Need a different LinkedIn surface? Pair this actor with any of the others in the LinkedIn Suite — all published under the same publisher and built to share the same cookie format and output conventions.

ActorWhat it scrapes
LinkedIn Comments ScraperAll comments + reply threads on a post
LinkedIn Company Employees ScraperEmployee list for any company (by URN)
LinkedIn Company Info ScraperCompany About page (size, HQ, industry, specialties)
LinkedIn Company Posts ScraperPosts published from a company page
LinkedIn Events ScraperEvents by keyword/URL with full event detail
LinkedIn Hashtag Posts ScraperPosts ranked under a #hashtag
LinkedIn Jobs ScraperJob listings via the public jobs-guest API
LinkedIn Jobs Scraper UltraSame as jobs-scraper + full detail enrichment
LinkedIn Learning Courses ScraperLinkedIn Learning course catalog by keyword
LinkedIn People Search ScraperPeople search with every LinkedIn facet (role, company, school, location, etc.)
LinkedIn Post Reactions ScraperReactors on a post (name, headline, reaction type)
LinkedIn Post ScraperFull post (text, media, engagement counts, author)
LinkedIn Profile Posts ScraperAll posts/reposts/articles for one profile
LinkedIn Profile ScraperPublic profile fields (name, headline, positions, education, skills)
LinkedIn Profile Scraper ProProfile fields + extras (recommendations, organizations, languages)
LinkedIn Profile Scraper Pro UltraPro + premium fields (contact info, followers list when allowed)
LinkedIn Profile Scraper UltraProfile + the full upstream dash-120 surface
LinkedIn Profile Search by NameSearch profiles by person name (great for matching CSVs of names)
LinkedIn Schools Alumni ScraperAlumni list for any LinkedIn school page
LinkedIn Top Content ScraperTrending / top-engagement posts by topic
LinkedIn User Activity ScraperReactions + comments + posts feed for one profile

All actors share the same cookie input format (plain li_at OR full cookies JSON array) and the same omit-empty output convention.