LinkedIn Company Posts Scraper - No Cookies

LinkedIn Company Posts Scraper extracts public posts from LinkedIn company pages in bulk, without requiring LinkedIn cookies or account credentials. Add company handles such as microsoft or full URLs such as https://www.linkedin.com/company/microsoft/, start the Actor, and get structured post data in an Apify dataset.

Use it to monitor competitors, track brand activity, collect B2B market signals, analyze company content strategy, or build automated reporting pipelines from public LinkedIn company page activity.

What can LinkedIn Company Posts Scraper do?

• Scrape LinkedIn company posts in bulk: process many company pages in one run instead of running one company at a time.
• No LinkedIn cookies required: extract public company page posts without asking users to share account sessions.
• Use simple company inputs: enter company handles, LinkedIn company URLs, or a pasted comma-separated list.
• Collect post content and engagement signals: extract post text, post URLs, dates, reaction counts, comment counts, repost counts, and reaction breakdowns when available.
• Extract media and article previews: capture public images, videos, document references, shared links, article titles, thumbnails, and domains when LinkedIn exposes them publicly.
• Control result size and cost: set the maximum number of posts per company and optionally filter posts by date.
• Automate workflows on Apify: schedule runs, monitor results, export datasets, use the Apify API, and connect results to Google Sheets, Make, Zapier, Slack, Airbyte, or your own data pipeline.

What data can you extract?

Data point	Description
Company name	Public display name of the LinkedIn company page when available.
Company handle	Normalized LinkedIn company identifier, such as microsoft.
Company URL	Canonical LinkedIn company page URL.
Post ID	LinkedIn post or activity identifier when available.
Post URL	Public URL of the company post.
Post text	Main visible text content of the post.
Published date	Normalized date or timestamp when available.
Raw date text	Original date text displayed by LinkedIn, useful when exact dates are not exposed.
Reaction count	Total public reaction count when available.
Reaction breakdown	Likes and other reaction categories when publicly available.
Comment count	Public comment count when available.
Repost count	Public repost/share count when available.
Media attachments	Images, videos, documents, or other public media references.
Article previews	Shared article URL, title, description, thumbnail, and domain when available.
Hashtags	Hashtags parsed from the post.
Mentions	Public mentions in the post when available.
Scraped timestamp	Time when the Actor saved the record.
Status and errors	Clear status for successful, unavailable, invalid, or failed company inputs.

Some LinkedIn fields may be missing for certain posts, regions, company pages, or public page layouts. Missing values are returned as null or empty arrays instead of being invented.

How to scrape LinkedIn company posts

1. Open the Actor on Apify.
2. Enter LinkedIn company handles such as microsoft, google, and meta, or paste full company URLs.
3. Set Max posts per company. The default is 100.
4. Optionally set Only posts since to collect newer posts only.
5. Keep Apify Proxy enabled for better reliability.
6. Click Start.
7. Open the Dataset tab to preview the results.
8. Export the dataset as JSON, CSV, Excel, XML, HTML, or JSONL.

For recurring monitoring, create an Apify Task from your input and schedule it to run daily, weekly, or at the interval your workflow requires.

Input

You can provide companies in several formats. The Actor accepts handles, full LinkedIn company URLs, and pasted bulk lists.

Input field	Type	Required	Description
companies	array	Yes, unless another company input is used	LinkedIn company handles or company URLs. Example: microsoft.
companyUrls	array	No	LinkedIn company page URLs in the format https://www.linkedin.com/company/{handle}/.
companyListText	string	No	Bulk pasted list separated by commas, semicolons, or new lines.
maxPostsPerCompany	integer	No	Maximum number of posts to extract per company. Default: 100.
onlyPostsSince	string	No	Optional date filter in YYYY-MM-DD format.
includeMedia	boolean	No	Extract media attachments and article previews when available.
includeReactionBreakdown	boolean	No	Extract reaction counts by type when available.
includeCompanyMetadata	boolean	No	Include company metadata on each result.
outputMode	string	No	Choose post records only or include company summaries/errors.
deduplicatePosts	boolean	No	Remove duplicate posts within the same run.
continueOnError	boolean	No	Continue with other companies if one company fails.
maxConcurrency	integer	No	Number of companies processed at the same time.
proxyConfiguration	object	No	Apify Proxy or custom proxy configuration.
browserFallback	boolean	No	Use browser fallback if HTTP extraction fails. Can increase cost.
debugMode	boolean	No	Save extra diagnostics for troubleshooting.

Example input

{
  "companyListText": "microsoft, https://www.linkedin.com/company/google/, meta",
  "maxPostsPerCompany": 25,
  "onlyPostsSince": "2026-01-01",
  "includeMedia": true,
  "includeReactionBreakdown": true,
  "outputMode": "posts",
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

Input tips

• Good: microsoft
• Good: https://www.linkedin.com/company/microsoft/
• Good: microsoft, google, meta
• Avoid profile URLs such as https://www.linkedin.com/in/someone/; this Actor is for company pages.
• Avoid jobs, school, feed, or search URLs unless they are explicitly supported in a future version.
• Duplicate companies are processed once.
• If onlyPostsSince is used, enter a date such as 2026-01-01, not last month.
• Higher company counts, higher post limits, browser fallback, and retries can increase runtime and Compute Unit usage.

Output

Results are saved to the default Apify dataset. Each post is stored as one dataset item, which makes the output easy to preview in Apify Console and export to JSON, CSV, Excel, XML, HTML, or JSONL.

You can also access the dataset through the Apify API, Python client, Node.js client, webhooks, or integrations.

Example output

{
  "recordType": "post",
  "inputIndex": 0,
  "originalInput": "microsoft",
  "companyHandle": "microsoft",
  "companyUrl": "https://www.linkedin.com/company/microsoft/",
  "companyName": "Microsoft",
  "companyDescription": "Technology company",
  "companyLogoUrl": "https://media.licdn.com/dms/image/example",
  "companyFollowerCount": 25800000,
  "postId": "urn:li:activity:7340000000000000000",
  "postUrl": "https://www.linkedin.com/posts/microsoft_example-activity-7340000000000000000",
  "postText": "Today we announced new AI capabilities for developers and organizations building secure, scalable applications.",
  "publishedAt": "2026-05-21T00:00:00.000Z",
  "publishedAtText": "3w",
  "reactionCount": 1842,
  "reactionCountText": "1,842",
  "commentCount": 96,
  "repostCount": 214,
  "reactions": {
    "like": 1450,
    "celebrate": 210,
    "support": 22,
    "love": 80,
    "insightful": 75,
    "funny": 5,
    "total": 1842
  },
  "hashtags": ["AI", "Developers"],
  "mentions": [],
  "links": [
    {
      "url": "https://blogs.microsoft.com/example",
      "text": "Learn more",
      "domain": "blogs.microsoft.com"
    }
  ],
  "media": [
    {
      "type": "article",
      "url": "https://blogs.microsoft.com/example",
      "title": "New AI capabilities for developers",
      "description": "An overview of new developer tools.",
      "thumbnailUrl": "https://example.com/article-preview.jpg",
      "domain": "blogs.microsoft.com"
    }
  ],
  "article": {
    "url": "https://blogs.microsoft.com/example",
    "title": "New AI capabilities for developers",
    "domain": "blogs.microsoft.com"
  },
  "postType": "article",
  "language": "en",
  "scrapedAt": "2026-06-17T10:04:30.000Z",
  "status": "ok",
  "errorMessage": null
}

How much does it cost?

Final pricing depends on the Actor pricing model configured by the publisher on Apify Store. Runtime cost may also depend on your Apify plan, Compute Unit usage, proxy usage, number of companies, number of posts per company, retry count, and whether browser fallback is enabled.

As a rule of thumb, fewer companies and lower post limits are faster and cheaper. Browser fallback can improve success for some pages but usually costs more than HTTP extraction. Scheduled monitoring can be efficient when combined with date filters such as onlyPostsSince. Check the Actor pricing panel on Apify Store before running large jobs.

LinkedIn company posts API, integrations, and automation

You can use this Actor as a hosted LinkedIn company posts API through Apify.

Common automation options:

• Apify API: run the Actor and fetch dataset items from your own application.
• Schedules: monitor selected LinkedIn company pages daily, weekly, or hourly.
• Webhooks: trigger a workflow when a run succeeds, fails, or finishes.
• Dataset exports: download results as CSV, Excel, JSON, XML, HTML, or JSONL.
• Integrations: send results to Google Sheets, Make, Zapier, Slack, Airbyte, or cloud storage.
• Python and Node.js clients: run the Actor and read results programmatically.

Useful Apify docs:

• Apify API: https://docs.apify.com/api/v2
• Datasets: https://docs.apify.com/platform/storage/dataset
• Webhooks: https://docs.apify.com/platform/integrations/webhooks
• Schedules: https://docs.apify.com/platform/schedules

Responsible use and legality

This Actor extracts public LinkedIn company page data. It is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation. LinkedIn is a trademark of LinkedIn Corporation.

You are responsible for ensuring that your use of the Actor complies with applicable laws, regulations, and platform terms. If your results include personal data, public mentions, names, or other information relating to individuals, privacy laws such as GDPR, CCPA, or other local rules may apply. Make sure you have a legitimate reason to collect and process the data.

This README is not legal advice. Do not use this Actor to access private data, bypass access controls, automate logged-in actions, or violate applicable terms.

FAQ

Can I scrape LinkedIn company posts without cookies?

Yes. This Actor is designed to extract public LinkedIn company page posts without asking for LinkedIn cookies or account credentials. Public availability can vary, and some pages or posts may be restricted or unavailable.

Does this Actor scrape personal LinkedIn profiles?

No. This Actor is for LinkedIn company pages. Profile URLs, jobs URLs, feed URLs, and unrelated LinkedIn URLs should be rejected or reported as invalid input.

How many companies can I process in one run?

The recommended maximum is up to 1000 unique companies per run. Large runs may take longer and may cost more because they require more requests, retries, and proxy traffic.

How many posts can I extract per company?

The recommended maximum is 100 recent posts per company. Some companies may return fewer posts if fewer public posts are available or LinkedIn does not expose older activity publicly.

Why are some fields null?

LinkedIn does not always expose every field publicly. Reaction breakdowns, exact dates, follower counts, repost counts, media metadata, or article previews may be unavailable for some posts. The Actor returns null or empty arrays rather than inventing values.

Can I export LinkedIn posts to CSV or Excel?

Yes. Open the Apify dataset after the run and export results as CSV, Excel, JSON, XML, HTML, or JSONL.

Can I run this Actor on a schedule?

Yes. Create an Apify Task from your input and set a schedule. For monitoring workflows, use onlyPostsSince to reduce old results and connect webhooks or integrations to send fresh output to your tools.

Is this an official LinkedIn API?

No. This is an independent Apify Actor for extracting public company page data. It is not an official LinkedIn API and is not affiliated with LinkedIn.

Troubleshooting

Problem	Possible cause	What to try
No companies were processed	Input was empty or invalid	Add at least one company handle or LinkedIn company URL.
A company failed with invalid input	The URL is not a LinkedIn company page	Use https://www.linkedin.com/company/{handle}/.
Some companies return no posts	The company has no public recent posts or public activity is restricted	Check the company page manually and reduce filters such as onlyPostsSince.
Reaction breakdown is missing	LinkedIn did not expose reaction details publicly	Use reactionCount when available and treat breakdown fields as optional.
Run is slow	Large company list, high post limit, retries, proxy latency, or browser fallback	Lower maxPostsPerCompany, reduce company count, or disable browser fallback.
Run is blocked or unstable	Target-site protection, high concurrency, or no proxy	Enable Apify Proxy and lower maxConcurrency.
CSV columns contain JSON arrays	Media, links, mentions, and reactions are nested fields	Export as JSON for nested data or flatten selected fields in your downstream workflow.
Some dates are approximate	LinkedIn may show relative dates such as 2w	Use publishedAtText for the original value and publishedAt when normalized.

Support and feedback

Use the Issues tab on the Actor page for bug reports, feature requests, or questions. Include the run ID, input example, and a short description of what happened. For custom enhancements such as CSV upload, cross-run deduplication, comment extraction, or custom output fields, open an issue with your use case.