LinkedIn Posts Scraper 📝 [No Cookies] — Only $2.5/1K 💰

You want to watch what one profile or company page publishes — without keeping a logged-in session alive, and without your scraper dying the day the cookie expires.

No login · no cookies · profiles and company pages · 20+ posts in under 5s

---

⚡ Highlights

• 100% No Cookies Required: Zero risk of account bans or expired sessions.
• Profiles & Companies Supported: Scrape both individual executive posts and official brand page announcements.
• Ultra-Affordable: Only $0.0025 per post ($2.50 per 1,000 posts) — 50% cheaper than API Maestro ($5.00/1K).
• Fast HTTP Speed: Extracts up to 20+ posts in under 5 seconds.

---

📥 Input

Field	Type	Description
targetUrls	array	LinkedIn profile or company page URLs
maxPosts	integer	Cap for the whole run, across every URL — not per URL (default 20)
proxyConfiguration	object	Proxy settings (optional)

maxPosts is a budget for the entire run. With 3 URLs and maxPosts: 20, the first URL can consume all 20 — the actor then stops the loop and never requests the other two, which come back with zero rows. Targets are fetched in the order you pass them, so put the one that matters first. If you want 20 posts from each of 3 profiles, set maxPosts: 60, or run one URL per run.

📤 Output

{
  "type": "DiscussionForumPosting",
  "authorName": "Satya Nadella",
  "authorUrl": "https://www.linkedin.com/in/satyanadella",
  "targetUrl": "https://www.linkedin.com/in/satyanadella",
  "headline": "...",
  "text": "Some more detail on the ROIC Intelligence App I built yesterday...",
  "datePublished": "2026-07-30T01:35:47.220Z",
  "postUrl": "https://www.linkedin.com/posts/satyanadella_some-more-detail-on-the-roic-intelligence-activity-7488406960443183104-g52O",
  "scrapedAt": "2026-08-19T12:28:00.000Z"
}

✅ Capabilities & Limits

Built here: each target is fetched with exactly one plain HTTP GET - no browser, no scrolling, no pagination, no retry. A non-200 (LinkedIn's 999, or 429) is logged and the URL is abandoned, so the post count per target is whatever LinkedIn embeds in that single guest HTML response and a partial IP throttle shrinks your dataset instead of failing the run.

What this actor does and does not do — stated up front, so you do not pay to find out.

Input / feature	Supported	Notes
Profile URL	✅	individual member pages
Company page URL	✅	official brand pages
Keyword search	❌	this actor reads known URLs — use linkedin-posts-search-pro
Comment text	❌	reaction and comment counts only
Private profiles	❌	public content only
Reactions by person	❌	aggregate counts, never who reacted
Per-URL post cap	❌	maxPosts is a run-wide budget — one URL can eat the whole quota (see the note under Input)
Reaction / comment counts	⚠️	shipped as interactionStatistic, and only for posts read from the page's JSON-LD block; posts recovered by the HTML fallback carry no counts field

🎯 Use cases

1. Competitor monitoring — track what rival brands announce and how it performs
2. Executive tracking — follow what decision-makers publish before a sales call
3. Content benchmarking — compare your posting cadence against a peer set
4. Newsjacking — catch announcements the moment they go up

❓ FAQ

Profiles or companies?
Both. Pass either URL type in targetUrls.

Will this get my account banned?
There is no account involved. No login, no cookies, nothing to ban.

Can I get who reacted?
No — only the counts. Identifying individual reactors is out of scope.

💰 Pricing

Pay Per Event. The rate depends on your Apify plan tier:

Plan tier	Per actor start	Per 1,000

You are never charged for a run that returned nothing. When the source blocks and nothing is extracted, the actor returns a labeled diagnostic and charges no PPE event.

---

🇧🇷 Português

Você quer acompanhar o que um perfil ou uma página de empresa publica — sem manter sessão logada e sem que o scraper morra no dia em que o cookie expira.

Sem login · sem cookies · perfis e páginas · 20+ posts em menos de 5s

Sem login e sem cookies. Preço por evento, com desconto por tier do seu plano Apify — veja a tabela acima. Execução que não retorna nada não é cobrada: quando a fonte bloqueia, o actor devolve um diagnóstico rotulado, sem cobrar evento.

maxPosts é orçamento da execução inteira, não por URL. Com 3 URLs e maxPosts: 20, a primeira URL pode consumir os 20; o actor encerra o laço e nem chega a requisitar as outras duas, que voltam vazias. As URLs são processadas na ordem em que você as envia. Para 20 posts de cada um dos 3 perfis, use maxPosts: 60.

Campos de entrada, saída, limites e FAQ estão nas seções em inglês acima.