Post and author
Canonical post identity, text, observed type, publication time, plus public author name, headline, profile, picture, and followers when exposed.
Available on Apify · by Meka
LinkedIn Public Post ScraperPublic content, ready to analyze.
Turn LinkedIn post URLs or activity IDs into structured records for monitoring, content research, enrichment, and AI workflows.
$1 per 1,000 delivered posts. No LinkedIn cookies.
Invalid, restricted, and duplicate inputs are not billed as results.
inPublic postFresh record from an anonymous public page
Text, author, media
Document post · Public company author
POST CONTENT
Capture the public text, canonical URL, publication time, attached media, repost context, and available engagement.
- Reactions
- Public total
- Comments
- Public count
- Export
- JSON / CSV
From a post URL to usable content.
Collect the public parts of a LinkedIn post without maintaining cookies, accounts, browsers, or parsing infrastructure.
Rich media
Images, video metadata, documents, article cards, attached jobs, and original-post details for accessible reposts.
Public engagement
Public aggregate reactions and comment count, with an explicit limitations array for data the source does not expose.
Public data only. Unavailable values are omitted rather than replaced with guessed zeros or nulls.
FROM URL TO DATASETYour first run.
Your first run.
Three simple steps.
Start with any anonymously accessible public LinkedIn post URL or numeric activity ID.
Run on Apify- 1
Add public posts
Paste one or more post URLs or activity IDs into the Actor input.
- 2
Run up to 1,000 inputs
Duplicate identities are fetched once while every physical input position remains represented in the Dataset.
linkedin.com/posts/... · or activity ID - 3
Use the records
Export JSON or CSV, schedule snapshots, or retrieve the ordered Dataset through the Apify API.
A small input. An auditable result.
Each input position produces either a successful public-post record or an explicit non-billable error record.
A predictable contract
Use the standard Apify Actor API, clients, CLI, schedules, or webhooks. Dataset order follows physical input order for safe downstream association.
View Actor API & documentation ↗An Apify account and API token are required for programmatic access.
EXAMPLE ACTOR INPUT
{
"postUrls": [
"https://www.linkedin.com/posts/google_7-ways-google-workspace-can-help-this-school-activity-7506056712026529793-gctk"
]
}Inspect output fields +
Core fields include postId, postUrl, text, postType, publishedAt, author, media, article, job, repost, engagement, fetchedAt, and limitations.
Do I need a LinkedIn account?+
No. The Actor reads anonymously accessible public post pages without a LinkedIn account, cookies, or browser session.
What inputs are supported?+
Provide one to 1,000 public LinkedIn post URLs or numeric activity IDs. Repeated post identities are fetched once and reported explicitly at later input positions.
How is it priced?+
Each successfully delivered post costs $0.001, equivalent to $1 per 1,000 records. Invalid, restricted, and duplicate inputs are not charged as delivered posts.
What can each record include?+
A record can include post text and type, publication time, public author details, images, native video metadata, documents, article and job cards, repost data, total reactions, and comment count.
Why are some engagement fields missing?+
LinkedIn public pages do not expose trustworthy reaction-category breakdowns, share counts, complete polls, or reaction-user lists. Meka omits unavailable values instead of guessing them.
Make public posts usable.
Start with URLs. Export structured content and context.