LinkedIn Search Posts Scraper (no cookies)
Pricing
from $6.00 / 1,000 runs
LinkedIn Search Posts Scraper (no cookies)
Search LinkedIn posts by keyword with engagement metrics and content entities
Pricing
from $6.00 / 1,000 runs
Rating
0.0
(0)
Developer
Data Direct
Maintained by CommunityActor stats
0
Bookmarked
9
Total users
3
Monthly active users
a month ago
Last modified
Categories
Security
Limited permissionsShare
LinkedIn Search Posts Scraper
Search for LinkedIn posts by keyword. Returns post content, author information, engagement metrics (likes, comments, shares, reactions), and attached content entities (images, articles, videos, job listings). Includes a has_content_entities flag, true when the post has an attached image, article, video, or job. Results can be sorted by most recent or relevance, and limited to posts from the past 24 hours, week, or month.
Features
- Real-time LinkedIn data — results are fetched live at run time, never cached or stale
- No login, cookies, or proxy configuration needed — just provide the input and run
- Each result is pushed as a separate dataset item, exportable as JSON, CSV, or Excel
- Fast: a typical run finishes in seconds
Input
| Field | Type | Required | Description |
|---|---|---|---|
query | string | no | Search query (max 500 characters). Required unless at least one filter (e.g. author) is provided. |
page | integer | no | Page number, 1-25 (default: 1). 20 posts per page. LinkedIn's search pool is at most ~500 posts per query, so pages past the pool return an empty list. Values below 1 are treated as 1; a page above 25 returns 400. |
sort_by | string | no | Sort order for results One of: most_recent, relevance. |
posted_ago | string | no | Only return posts from this period: 24h (past day), 7d (past week), or 30d (past month). Works with both sort orders and every filter. Omit for all time. Any other value returns 400. One of: 24h, 7d, 30d. |
author | string | no | Filter to posts authored by a specific person. Accepts a profile URL, public slug (e.g. williamhgates), or member URN, resolved automatically. Comma-separate for multiple (max 5 values). |
mentions_member | string | no | Filter to posts that mention a specific person (profile URL, slug, or member URN). Comma-separate for multiple (max 5 values). |
from_company | string | no | Filter to posts authored by a company page. Numeric LinkedIn company ID (from the Company Details scraper). Comma-separate for multiple. Non-numeric values return 400. |
author_company | string | no | Filter to posts written by people who work at a company. Numeric company ID, comma-separate for multiple. Non-numeric values return 400. |
mentions_company | string | no | Filter to posts that mention a company. Numeric company ID, comma-separate for multiple. Non-numeric values return 400. |
author_title | string | no | Filter by the author's job title as free text (e.g. CEO). Requires a query parameter. |
author_industry | string | no | Filter by the author's industry. Numeric LinkedIn industry ID(s), comma-separated. Requires a query parameter. Non-numeric values return 400. Advanced. |
Pricing
This Actor is billed per run — a flat $0.006 per run.
- One run returns all matching results for your input, and costs $0.006 — whether it comes back with one result or hundreds.
- You’re only charged when a run succeeds, or when it fails because what you asked for was looked up and doesn’t exist, is private, or isn’t valid: that costs one run ($0.006). Other failed runs are free.
Example output
{"article": null,"author": "Sina S. Amiri","comments": 0,"date": "2026-04-04 21:13:18","domain": "linkedin.com","has_content_entities": false,"images": [],"job": null,"likes": 5,"reactions": {"interest": 1,"like": 4},"shares": 0,"snippet": "In many practices and DSOs, artificial intelligence isn\u2019t fixing bad processes.\n\nIt\u2019s scaling unnecessary complexity.\n\nAnd when complexity scales, inefficiencies don\u2019t just persist.\n\nThey compound into operational drag and financial leakage.\n\nFaster.\n\nLarger.\n\nHarder to unwind.\n\nOrganizations should simplify before they automate, and eliminate before they optimize.\n\nBecause if AI is doing the work, you should first ask why the work exists at all.\n\n#Dentistry #ArtificialIntelligence #Technology #Operations #Strategy","source": "LinkedIn","title": "@Sina S. Amiri on LinkedIn","url": "https://www.linkedin.com/posts/betterdentistry_dentistry-artificialintelligence-technology-activity-7446303912871071744-Z5Ju?utm_source=social_share_send&utm_medium=member_desktop_web&rcm=ACoAAGaiQmMBKfdufODH2pNGp0lL6bF8EztcFWs","urn": "urn:li:activity:7446303912871071744","video": null}
About
Maintained by Data Direct — a small suite of fast, reliable LinkedIn and web-data scrapers. Each actor returns clean, structured results with no login, cookies, or proxy setup required. Have a question or a custom data need? Open an issue on this actor.