LinkedIn Post Scraper - Extract Post Data by URL avatar

LinkedIn Post Scraper - Extract Post Data by URL

Pricing

from $2.00 / 1,000 results

Go to Apify Store
LinkedIn Post Scraper - Extract Post Data by URL

LinkedIn Post Scraper - Extract Post Data by URL

Scrape a single LinkedIn post by URL. Extracts post text, author, timestamp, reactions, comment count, reposts, and media. No login or cookies needed.

Pricing

from $2.00 / 1,000 results

Rating

0.0

(0)

Developer

Thirdwatch

Thirdwatch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Share

LinkedIn Post Scraper

Extract structured data from a public LinkedIn post given its URL. Pure HTTP — no browser, no login, no cookies required.

What it does

Given one or more LinkedIn post URLs, returns:

FieldDescription
urlCanonical post URL
urnurn:li:activity:{id} / urn:li:share:{id} / urn:li:ugcPost:{id}
post_idNumeric id (last segment of the urn)
textFull post body (not the truncated og:description)
posted_relativeRelative timestamp as LinkedIn renders it (e.g. 1mo, 3d, 5h)
editedtrue if the post shows an "Edited" marker
author_nameAuthor display name
author_headlineAuthor tagline (job title / description)
author_profile_urlLink to the author's profile or company page
author_profile_imageAuthor avatar URL
author_is_companytrue if the author is a company page
reactions_countTotal reactions (likes, celebrates, etc.)
comments_countNumber of top-level comments
reposts_countAlways null — LinkedIn does not expose this on the public embed
mediaArray of {type, url, thumbnail} for images and videos in the post

Accepted URL formats

The actor accepts any of:

https://www.linkedin.com/posts/{user}_{slug}-activity-{id}-{hash}
https://www.linkedin.com/feed/update/urn:li:activity:{id}/
https://www.linkedin.com/feed/update/urn:li:share:{id}/
https://www.linkedin.com/feed/update/urn:li:ugcPost:{id}/
urn:li:activity:{id}

Query strings (e.g. ?actorCompanyId=...) are stripped automatically.

Input

{
"postUrls": [
"https://www.linkedin.com/feed/update/urn:li:activity:7444032259956903936/",
"https://www.linkedin.com/feed/update/urn:li:share:7441772941413085184/"
],
"maxPosts": 10
}

Output (per post)

{
"url": "https://www.linkedin.com/feed/update/urn:li:activity:7444032259956903936/",
"urn": "urn:li:activity:7444032259956903936",
"post_id": "7444032259956903936",
"text": "LinkedIn is currently chock-a-block with AI hype...",
"posted_relative": "1mo",
"edited": true,
"author_name": "Saranya Balachandran",
"author_headline": "Content Marketer & Strategist...",
"author_profile_url": "https://in.linkedin.com/in/saranya-balachandran-69443720",
"author_profile_image": "https://media.licdn.com/...",
"author_is_company": false,
"reactions_count": 27,
"comments_count": 5,
"reposts_count": null,
"media": [
{"type": "image", "url": "https://media.licdn.com/...", "thumbnail": ""}
]
}

Limitations

  • Comment text is not returned. Pulling individual comments requires a logged-in session; this actor stays purely public.
  • Reposts count is null. LinkedIn does not expose it on the public embed page.
  • posted_relative is a relative string, not an ISO timestamp. The public embed exposes only the rendered "1mo" / "3d" form. If you need an absolute timestamp, derive it client-side from post_id (LinkedIn ids encode the creation millisecond in the upper bits) or from your scrape time minus the relative interval.

Pricing

Pay-per-event: starts at $0.005 per post (FREE tier), drops to $0.002 at GOLD tier.