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

Collectors · Company data

LinkedIn company posts scraper in Python

Recent posts on public LinkedIn company pages, with exact reactions, comments and dates. One POST from Python with companies, rows back as JSON with 23 fields, $0.001 per delivered post. No proxies or parsers to maintain.

Get an API keySee the collector

First call

Install, call, read the rows.

pip install requests
The only dependency.
import os, requests

r = requests.post(
    "https://api.quanticdata.io/v1/scraper/collectors/linkedin_company_posts/run",
    headers={"Authorization": f"Bearer {os.environ['QD_API_KEY']}"},
    json={
        "companies": ["microsoft"],
        "max_results": 10,
    },
    timeout=120,
)
r.raise_for_status()
run = r.json()["payload"]
print(run["count"], "rows,", run["cost"]["usd"], "USD")
for row in run["results"]:
    print(row.get("company"), row.get("company_name"), row.get("post_id"), row.get("post_urn"))
Python: one LinkedIn company posts run (Microsoft), printing company, company_name, post_id, post_urn

The key comes from an environment variable, never from the code. The run answers in the same request when it finishes in time; payload.results holds the rows and payload.cost what they cost.

Request parameters

What the collector takes.

Input of the LinkedIn company posts collector
ParameterTypeRequiredMeaning
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_resultsintegerno (default 20)How many posts to deliver at most (1–200). You pay only for delivered posts.

Response fields

23 fields per post.

Fields of each row (post)
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.

Add ?format=csv to the runs endpoint to get the same rows as CSV.

Long runs

Run in the background, then poll.

A run that needs more time can go to the background: send "async": true, get 202 with the run id, and poll the runs endpoint until the status is done. Reading a run is free.

import os, time, requests

H = {"Authorization": f"Bearer {os.environ['QD_API_KEY']}"}
r = requests.post("https://api.quanticdata.io/v1/scraper/collectors/linkedin_company_posts/run", headers=H,
                  json={**{"companies":["microsoft"],"max_results":10}, "async": True}, timeout=30)
run_id = r.json()["payload"]["run_id"]
while True:
    run = requests.get(f"https://api.quanticdata.io/v1/scraper/collectors/runs/{run_id}", headers=H, timeout=30).json()["payload"]
    if run["status"] in ("done", "failed"):
        break
    time.sleep(5)
print(run["status"], run["count"])
Python: background run and polling

Errors

What can come back, and what is billed.

Collector run errors
StatusMeaningBilled
400The input does not match the collector (payload.errors)No
401Missing or wrong API keyNo
402Balance and free credit do not cover the run: top upNo
422The input can never resolve; retrying the same input cannot helpNo
424The run failed at the source (blocked, timed out, layout changed); safe to retryNo
429Rate limit or a per-account brake; wait for Retry-AfterNo

Only delivered rows are billed: a run that delivers nothing costs nothing.

Price

$0.001 per delivered post.

What LinkedIn company posts rows cost at list price
RowsCost
1$0.001
1,000$1.00
10,000$10.00

Up to 200 posts per run; split larger jobs into several runs. The $2 free credit every month covers about 2,000 posts. No subscription; paid tiers lower the unit price. All collector prices: collector pricing.

Before you run it

Questions developers ask

Is there a free LinkedIn company posts API?

Every account gets $2 of free usage each month, about 2,000 posts of this collector at $0.001 each, with no card.

Do I have to handle proxies, retries or blocks?

No. The collector runs on our network and handles them; a run blocked at the source returns 424 and is not billed.

How many rows can one run return?

Up to 200 posts per run (the max_results input, where the collector has one).

Can an AI agent run it?

Yes: the MCP server exposes it as the run_collector tool, with the same input and price. See the MCP server.

Run it on the free credit.

Create an API key, export it as QD_API_KEY and run the example. $0.001 per delivered post, no subscription.

Get an API keyLinkedIn company posts scraper