Documentation Python quickstart Blog Free tools Enterprise solutions hello@quanticdata.ioLog in
All collectors

LinkedIn company posts scraper

Company data · v1.0.0 · linkedin_company_posts

$0.001 / post

$1.00 / 1K · pay per delivered post

A LinkedIn company posts scraper that reads the public feed of any company page and returns each post as a row: the text, who wrote it, whether it is a repost, exact reaction and comment counts, the exact publish date and the date the company shared it, and the media. No login and no cookies, billed per post delivered.

$0.001 per delivered post · $2 free every month · Failed runs never billed

What it does

What a LinkedIn company posts scraper does

A company feed is the public log of what a business wants seen: launches, events, hires, the posts it chooses to amplify. Read every week, it shows what a competitor or a prospect is pushing before it reaches a press release. The collector reads that feed from the public company page, the one anyone sees without an account, and returns the posts as rows, about ten of the most recent per company.

The numbers come back exact. On 30 October 2026 we read Microsoft’s page: 10 posts on the feed, 6 of them reposts, the most reacted at 13,301 reactions and 639 comments. One repost had been published on 22 October and reached Microsoft’s feed on 27 October, while the card only said “1w”. Every row carries both dates, published_at and shared_at, so a weekly read can tell a new post from an old one shared again.

Inputs

The whole request. Anything you leave out falls back to the default shown in the catalog.

InputTypeRequiredWhat it does
companiesstring[]yesCompany page slugs (microsoft) or linkedin.com/company/ URLs, one per line, up to 20.
countrystringnoISO 3166-1 alpha-2 code — proxy exit geo and Google locale (gl). Omit for the default pool.
max_resultsintegernoHow many posts to deliver at most (1–200). You pay only for delivered posts.

Outputs — 23 fields, one row per post

What one post looks like

Every delivered post carries these fields. Nullable means the source did not publish it — the field stays empty instead of being guessed.

FieldTypeWhat it holds
companystringCompany page slug the post was read from.
company_namestring · nullableCompany name.
post_idstringNumeric id of the original post.
post_urnstring · nullableLinkedIn URN of the original post (urn:li:ugcPost:… or urn:li:share:…).
activity_idstring · nullableNumeric id of the activity on the company feed.
urlstringPost URL.
author_namestring · nullableWho wrote the post.
author_urlstring · nullableAuthor profile or company page URL.
author_is_companybooleanTrue when the author is a company page.
by_companybooleanTrue when the author is this company itself.
is_repostbooleanTrue when the company reposted someone else's post.
textstring · nullablePost text.
published_atstring · nullableWhen the original post was published (ISO 8601, exact, not the “2w” on the card).
shared_atstring · nullableWhen it appeared on this company’s feed (ISO 8601); later than published_at for a repost.
age_labelstring · nullableThe age LinkedIn prints on the card (21h, 2d, 1w).
reactionsinteger · nullableExact reaction count.
commentsinteger · nullableExact comment count.
media_typestringvideo, live, images, article or text.
image_countintegerImages attached to the post.
video_titlestring · nullableTitle of a live video post.
article_titlestring · nullableTitle of a linked article.
article_urlstring · nullableURL of a linked article.
rankinteger1-based delivery order.

Integration

One POST, typed rows

Base URL https://api.quanticdata.io/v1, Bearer auth, the same key as every other Data API. Endpoint: POST /v1/scraper/collectors/linkedin_company_posts/run.

curl -X POST https://api.quanticdata.io/v1/scraper/collectors/linkedin_company_posts/run \
  -H "Authorization: Bearer $QD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"companies":["microsoft"],"max_results":10}'

Example response

POST /v1/scraper/collectors/linkedin_company_posts/run
$ curl $QD/linkedin_company_posts/run \
    -H "Authorization: Bearer $QD_API_KEY" \
    -d '{"companies": ["microsoft"], "max_results": 10}'
{ "status": "done", "count": 10,
  "results": [
    {
      "company": "…",
      "text": "…",
      "reactions": "…",
      "published_at": "…" } ],
  "cost": 0.01 }
# 10 posts × $0.001 · nothing delivered, nothing charged

Try it

LinkedIn company posts, running now

Change the input and run it against the live collector — nothing to install, no sign-up.

Run it from your own code, on your own inputs

Same collector, same rows — $2 of free API credit every month, no card.

Get my free API key
LinkedIn company posts scraper: from companies, QuanticData reads the LinkedIn company posts scraper page and returns one row per post with company_name, post_urn and author_name, at $0.001 per delivered post.
You send company pages; the posts on their public feed come back as rows with company, text and exact reactions — 23 fields on every row — and you are billed $0.001 for each post actually delivered, nothing for a run that delivers none.
$0.001 / post2,000 posts on the free $2 every month
Semantic inputcompanies, country, max_results — no URL lists
Up to 200posts per run, pagination handled for you
23 fieldsone row per post

Pricing

LinkedIn Company Posts Scraper pricing

$0.001 per delivered post. A run that delivers nothing costs nothing, and the $2 monthly allowance covers about 2,000 posts before you spend anything.

$0.001per delivered post$1.00 per 1,000 delivered posts
2,000 postson the free allowance$2 every month, no card
Zero rowszero chargea run that delivers nothing is free
−30%on volume tiersthe catalog returns your key's price

Same wallet, same key and same $2 monthly allowance as every other Data API. Prices are launch pricing read live from the billing config — GET /v1/scraper/collectors returns the price your key actually pays.

What people build with the LinkedIn company posts scraper

Three shapes of work this endpoint was designed around.

Competitor monitoring

Read the feeds of the companies you track every Monday and keep the rows: what each one launched, announced or amplified that week, and how much engagement it got.

Account-based selling

A post about a new office, a product or a hiring push is a reason to call. Read your target accounts’ feeds and route those posts to the owner of the account.

Content benchmarks

Exact reactions and comments per post, by media type, across a set of pages: which formats work in your industry, measured instead of assumed. Pair it with the LinkedIn company scraper API for followers and employees.

LinkedIn Company Posts Scraper versus rolling your own

The differences that actually cost time when you build this in-house.

DIY scraperThis collector
Getting the pageA logged-in browser and an account at riskThe public company page, no login, no cookies
DatesThe “2w” printed on the cardExact publish and share dates, ISO 8601
EngagementRounded labels to parseExact reaction and comment counts as integers
RepostsMixed in with the company’s own postsFlagged, with the original author and both dates
MediaRead the card and guessMedia type, image count, article title and link as fields
BillingRequests, successful or notOnly delivered posts
LinkedIn company posts scraper: the POST to the linkedin_company_posts collector, 10 posts delivered and the bill, 10 × $0.001 = $0.01 in usage.cost_usd; zero posts would cost $0.
The same call you would paste into a terminal: a Bearer key, the companies in the body, and back the envelope every QuanticData endpoint returns — type, message, payload — where count is how many posts arrived and usage.cost_usd is $0.01, which is 10 × $0.001. A run that delivers nothing costs nothing.

Sources and standards

The platform documentation and standards this collector is built against — check any claim on this page against the primary source:

FAQ

Questions we get about the LinkedIn company posts scraper.

Something else? Ask us

Can you scrape LinkedIn posts without logging in?

Yes, for company pages. The collector reads the public company page, the one anyone can open without an account, and delivers the posts its feed shows: about ten of the most recent per company. It never logs in and never uses cookies, so no account of yours is involved.

How do I get company posts from LinkedIn by API?

Send company slugs or page URLs to POST /v1/scraper/collectors/linkedin_company_posts/run with your API key: up to 20 companies in one run, rows back as JSON, or as CSV from the dashboard. LinkedIn’s own Posts API is for the pages you administer, after an access review; this reads the public feed of any company.

Does LinkedIn allow scraping?

The collector reads only what LinkedIn shows to a visitor who is not signed in, and only company pages. How you may use the data depends on LinkedIn’s User Agreement and on the law where you work, so check both for your use case.

How many posts do I get per company?

The posts the public feed shows, about ten of the most recent. Ask for several companies in one run and the rows come back together, each with the company it was read from in company.

Is there a free LinkedIn company posts scraper?

Every account gets $2 of credit every month with no card, which is about 2,000 delivered posts on this endpoint at $0.001 each. It renews monthly, and a run that delivers nothing is never billed.

How much does one run cost?

Multiply the rows you actually receive by $0.001. A run capped at 200 posts — the maximum for this collector — costs $0.2 if every row comes back, and less when the listing has fewer. Volume tiers take up to 30% off, and GET /v1/scraper/collectors returns the price your key actually pays.

Run the LinkedIn company posts scraper now

$2 of free credit every month, no card. Your key returns its own prices from GET /v1/scraper/collectors.

Get my free API key
Illustration: three coloured zones of the page that is read (LinkedIn company posts scraper page) turn into clean JSON with the fields company_name, post_urn and author_name; 23 fields on every row.