Skip to content
ScrapeField

Get one LinkedIn post

Fetch one post by its URL: its text, images, author, published_at, reaction_count and comment_count. repost_count and the reactions by kind are null: the source gives the total only. Use linkedin/comments for its comments and linkedin/reactions for who reacted.

3credits
GEThttps://api.scrapefield.com/v1/linkedin/post
Try itno key needed3 credits on a real call · 0 here
https://api.scrapefield.com/v1/linkedin/post?url=https%3A%2F%2Fwww.linkedin.com%2Fposts%2Fferrari_ferrari-activity-7513660751346184192-VA32

In your code

const params = new URLSearchParams({
  "url": "https://www.linkedin.com/feed/update/urn:li:activity:7243000000000000000"
});

const res = await fetch(`https://api.scrapefield.com/v1/linkedin/post?${params}`, {
  headers: { Authorization: `Bearer ${process.env.SCRAPEFIELD_KEY}` },
});

const { data, meta } = await res.json();
console.log(data, meta.credits_charged);

Parameters

ParameterWhat it does
url
string · required
The post's URL: https://www.linkedin.com/posts/…-activity-<id>-…, or https://www.linkedin.com/feed/update/urn:li:activity:<id>. A link by the share's id works too: urn:li:ugcPost:<id>, urn:li:share:<id> or /posts/…-ugcPost-<id>-….
fresh
boolean
Skip the cache and fetch now. Charged normally. Not available on trial credits — buy any pack to unlock it.
default false

Response

Returns one linkedin_post. This is the demo’s answer, the one the playground above returns, in full rather than abbreviated — including the fields that come back null, because a field is null when the platform does not show it and you should know which ones those are before you build on them. A call with your key returns the account you ask for.

{
  "data": {
    "urn": "urn:li:activity:7243000000000000000",
    "url": "https://www.linkedin.com/feed/update/urn:li:activity:7243000000000000000/",
    "author": {
      "name": "Blue Door Coffee",
      "type": "company",
      "headline": "80,871 followers",
      "url": "https://www.linkedin.com/company/blue-door-coffee/"
    },
    "text": "Hiring: two backend engineers, remote in Europe. The stack is boring on purpose.",
    "published_at": "2026-07-27T07:36:00.000Z",
    "reaction_count": 538,
    "reactions": null,
    "comment_count": 7,
    "repost_count": null,
    "images": [],
    "video": null,
    "document": null,
    "article": null,
    "is_repost": null
  },
  "meta": {
    "request_id": "req_7f3ac1e94b2d40f8a1c6e5d2",
    "credits_charged": 3,
    "credits_remaining": 74218,
    "cached": false,
    "fetched_at": "2026-09-20T09:12:03Z",
    "next_cursor": null
  }
}

Fields of linkedin_post

A LinkedIn post. Named after the words LinkedIn prints, since LinkedIn has no official data API.

FieldWhat it is
urn
string
LinkedIn's id for the post, e.g. urn:li:activity:7243….
url
URL
The post.
author
object
Who posted it: a person or a company page.
author.name
string · or null
null where the source names only the page.
author.type
string, one of
Whether a person or a company page posted it.
person · company
author.headline
string · or null
The person's headline, or the company's follower line.
author.url
URL
Their profile or company page.
text
string · or null
The post's text.
published_at
time, ISO 8601 UTC · or null
null where the source does not say.
reaction_count
integer · or null
All reactions together. null where the source does not give the counts.
reactions
object · or null
By kind, where LinkedIn shows the breakdown.
reactions.like
integer
Like reactions.
reactions.celebrate
integer
Celebrate reactions.
reactions.support
integer
Support reactions.
reactions.love
integer
Love reactions.
reactions.insightful
integer
Insightful reactions.
reactions.funny
integer
Funny reactions.
comment_count
integer · or null
How many comments. null where the source does not give it.
repost_count
integer · or null
How many reposts. null where the source does not give it.
images
array of URLs
Image URLs, in order.
video
object · or null
A video in the post.
video.url
URL
The video file.
video.duration
integer · or null
Seconds.
document
object · or null
An attached PDF or slide deck.
document.title
string
The document's title.
document.page_count
integer · or null
How many pages it has.
article
object · or null
A shared link.
article.title
string · or null
The title the link's preview shows.
article.url
URL
Where the link leads.
is_repost
boolean · or null
Whether this is someone else's post reposted without comment. null where the source does not say.

What it costs

3 credits per successful call, whether we fetch it or serve it from cache — you pay for the answer, not for how we produced it. Responses are cached for 3 hours and a cached one tells you when the data was actually fetched. A call we fail costs 0 and is refunded automatically.

On the smallest pack that is $2.34 per 1,000 calls; on the largest, $1.32. The full table.

Questions

How much does the LinkedIn post details API cost?

3 credits a call: $2.34 per 1,000 calls on the smallest pack and $1.32 on the largest. A call that fails costs nothing, and the refund is automatic. A cached answer costs the same as a fresh one. Credits are bought in packs and never expire; there is no subscription.

Do I need a LinkedIn account, a login or cookies?

No. You need a key from us and nothing from LinkedIn. We never take a customer's login, cookies or session, at any price, and no account of yours is ever at risk.

Can I try it without signing up?

Yes. Add demo=true and leave the key out, or press Send request in the playground on this page. The demo answers with a real answer about Ferrari, captured once a week, in exactly the shape a live call returns, whatever you ask, and charges nothing.

How fresh is the data?

An answer is kept for up to 3 hours, and a cached one says when it was fetched, in meta.fetched_at. Add fresh=true to fetch it again now, at the same price; it needs any purchase, not the trial.

What does it return?

One linkedin_post object. Its fields are named after the words LinkedIn prints, since LinkedIn has no official data API. A field is null when LinkedIn does not show it, never missing. Every field is described on this page.

Can an AI agent call it?

Yes: it is the MCP tool get_linkedin_post on our MCP server, with the same parameters, answer and price. Without a key, the tool answers from the demo.