# LinkedIn Company Posts Scraper \[NO COOKIES] ✅ (`unseenuser/company-posts`) Actor Scrape a LinkedIn company's all recent posts in one run. Get full post text, engagement, and posting cadence. No login, no cookies. Built for ABM, competitive intel, and content strategy teams. - **URL**: https://apify.com/unseenuser/company-posts.md - **Developed by:** [Unseen User](https://apify.com/unseenuser) (community) - **Categories:** Social media, Lead generation, Jobs - **Stats:** 4 total users, 2 monthly users, 100.0% runs succeeded, 4 bookmarks - **User rating**: 5.00 out of 5 stars ## Pricing $4.00 / 1,000 results This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp.md). If your project is in a different language, use the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## 🏢 LinkedIn Company Posts Scraper - Every Post from Any Company Page (No Login) Scrape every post from a LinkedIn company page with full engagement metrics. **No login.** --- ### Free plan limit Free Apify users get up to **50 posts per run** (counted across all company URLs you submit). Paying users are not affected and receive posts normally. This limit was set by the Actor developer, not by Apify. To remove it and receive unlimited posts, upgrade to any paid Apify plan: https://apify.com/pricing When a free plan run hits the cap, the Actor finishes successfully (status `SUCCEEDED`) and the run's status message explains what happened. No error is raised, so the first 50 posts are fully usable as normal. --- ### 🎯 Use Cases - **Competitive monitoring** - track what competitors are posting and how their audience reacts - **Content marketing benchmarking** - see what topics industry leaders post about and how often - **Sales enablement** - equip reps with a target company's latest LinkedIn content before calls - **Brand monitoring** - detect mentions, tone shifts, or crisis posts on competitor pages - **Trend research** - collect posts across many companies to find what's resonating in a sector ### 🚀 Quick Start 1. Click **Try for free** on this Actor's page 2. Paste **one or more** LinkedIn company URLs into the **LinkedIn company URLs** field (it's prefilled with `https://www.linkedin.com/company/google` as an example - add more rows for bulk scraping) 3. Click **Start** 4. Download the output as JSON, CSV, or XLSX, or pull via Apify API You get **one dataset row per post**, so the row count in your Apify dashboard always equals the number of posts you actually got. ### ⚙️ Input Fields All inputs live in a single flat form: | Field | Description | | ------------------------------------- | ------------------------------------------------------------------------------------------------------ | | **LinkedIn company URLs** | One or more LinkedIn company URLs. Click **+ Add** to scrape multiple companies in a single run. Example: `https://www.linkedin.com/company/google`. | | **How many posts to fetch per company** | Per-company post cap. Set to `0` to fetch every available post. Default `100`. Max `1000`. | | **Posted within** | Time window: `All time`, `Last hour`, `Last 24 hours`, `Last week`, `Last month`, `Last 3 months`, `Last 6 months`, `Last year`. | ### 💰 Pricing Pay-per-event model on Apify. Each Apify run consumes N HarvestAPI page calls under the hood (one per page of ~20 posts). See exact per-event pricing on the Actor's Apify page. ### ❓ FAQ **Q: Does this also return company profile data (industries, employee count, funding)?** A: No. This Actor is posts-only by design. If you need company profile data, use the sibling scraper [LinkedIn Company Scraper Pro](https://apify.com/unseenuser/LinkedIn-Company-Scraper). **Q: Is this legal?** A: This Actor wraps HarvestAPI's posts endpoint that handles the underlying data collection. Your downstream use of the data is your responsibility - see the full Terms of Service and Actor-Specific Addendum below for details. **Q: What if LinkedIn sends a cease-and-desist?** A: Notify UnseenUser within 48 hours via the Apify profile contact form (https://apify.com/UnseenUser) and cease using this Actor immediately. **Q: Can I use this data to train AI?** A: No. LinkedIn's Terms explicitly prohibit AI training on LinkedIn data, and post authors retain copyright. See Addendum Section G. ### 🔧 Technical Details - **Endpoint:** HarvestAPI `/linkedin/company-posts`, paginated - **Retries:** 3 with exponential backoff (1s, 2s, 4s) on `429` / `502` / `503` / `504` - **Output:** streamed via Apify dataset, one row per post - **Format:** JSON, CSV, XLSX, or via Apify API --- ### 📡 Output Reference #### Output Structure One dataset row per post: ```json { "post": { "/* full PostShort object: id, content, linkedinUrl, author, postedAt, engagement, ... */": true }, "_metadata": { "scraped_at": "2026-05-25T12:34:56.789Z", "company_url": "https://www.linkedin.com/company/google", "post_index": 0, "total_posts_for_company": 50 } } ```` Submit 1 URL with 100 posts and you get 100 rows. Submit 5 URLs with 20 posts each and you get 100 rows. The Apify dashboard's "results" count always equals the number of posts. If a URL has zero posts (or the page doesn't exist), a single row is pushed with `post: null` and a structured `error` field. Failed URLs also push one row each with the `error` field. #### Error Handling - No Crashes, Just Fix-It Rows This Actor **never throws raw errors**. If something is wrong (missing input, missing API key, company page not found, posts request failed), it pushes a single dataset row with a structured `error` field and exits cleanly. You always get a row you can inspect. ```json { "post": null, "_metadata": { "scraped_at": "2026-05-25T12:34:56.789Z", "company_url": "" }, "error": { "type": "missing_input", "message": "No LinkedIn company URLs were provided.", "fix": "Open the Actor input, paste a LinkedIn company URL into the 'LinkedIn company URLs' field..." } } ``` Possible `error.type` values: | `type` | When it happens | | ------------------------- | ------------------------------------------------------------ | | `missing_input` | No URL was supplied or none of the URLs look like LinkedIn company pages. | | `missing_api_key` | The `HARVEST_API_KEY` env var is not set. | | `company_not_found` | The LinkedIn URL returned 404 from HarvestAPI. | | `posts_request_failed` | Posts endpoint failed mid-pagination - any pages already fetched are still pushed. | | `unexpected` | An unforeseen internal error - report via Apify profile. | Every error row includes a human-readable `fix` field that tells you exactly what to do next. ### 📊 Output Schemas The repo ships these schemas Apify uses to render your output: - **`.actor/output_schema.json`** - the Output schema. Declares that this Actor produces a primary `dataset` output and surfaces a short description users see in the Apify Console. - **`.actor/dataset_schema.json`** - dataset rendering hints. Ships the **Posts** view: a flat table of every post with its engagement metrics and source URL. - **`.actor/key_value_store_schema.json`** - documents the `INPUT` collection in the default key-value store. - **`.actor/input_schema.json`** - the flat input form described above. This Actor does not expose a live web server, so no OpenAPI schema is shipped. *** ### 🛡️ Apify Actor - Terms of Service **Version:** 4.0 **Effective Date:** May 5, 2026 #### 0. ACCEPTANCE BY USE - IMPORTANT Read this section first. These Terms of Service ("Terms") form a binding legal agreement between you ("User," "you," "your") and **UnseenUser**, the Publisher of this Apify actor ("UnseenUser," "the Publisher," "we," "us," "our"). ##### 0.1 How You Accept These Terms You accept these Terms by any of the following actions, each of which constitutes a clear, affirmative act of acceptance: - (a) **Running the Actor** - Initiating any execution of the Actor on the Apify platform - (b) **Using any output returned by the Actor** for any purpose - (c) **Continuing to access** the Actor's listing or documentation after these Terms are visible ##### 0.2 Continuing Acceptance Each time you run the Actor or use its outputs, you reaffirm your acceptance of the then-current Terms. If you do not agree to these Terms or any subsequent update, you must stop using the Actor immediately. ##### 0.3 No Anonymous Acceptance You cannot disclaim acceptance by: - Failing to read these Terms before running the Actor - Running the Actor through automated systems - Sharing your Apify account with others who may not have read these Terms By the act of running the Actor on Apify, you bind yourself, your organization (if applicable), and any individuals or systems acting on your behalf or under your authority. ##### 0.4 If You Do Not Accept If you do not agree to these Terms, you must not run the Actor. No use is authorized without acceptance. #### PREAMBLE - UNDERSTANDING THE ARCHITECTURE Before using the Actor, please understand the technical architecture of the service: ##### The Data Flow ``` You (User) → Apify Platform → Actor (software) → Third-Party API → Source Platform ↓ You (User) ← Apify Platform ← Actor (software) ← Third-Party API ``` ##### What Each Party Does - **You (the User):** Run the Actor on the Apify platform with input parameters you choose - **Apify:** Operates the cloud infrastructure that hosts and executes Actors. Apify is a Czech-incorporated company (Apify Technologies s.r.o.) governed by its own Terms of Service. - **The Publisher (us):** Publishes software code (the Actor) on Apify's platform. The Actor is a thin wrapper that translates your input into requests to a third-party API and returns the API's responses to you. The Publisher does not operate scraping infrastructure. The Publisher does not store or retain data returned by the Actor. The Publisher does not see, log, or process the personal data of any individuals returned in the Actor's outputs beyond what is incidental to passing the data through. - **Third-Party API Provider:** HarvestAPI (https://harvest-api.com) or Scrape Creators (https://scrapecreators.com). These are independent third-party companies that operate scraping infrastructure and return data from source platforms. - **Source Platform:** LinkedIn, TikTok, YouTube, Reddit, Linktree, etc. These are the platforms whose publicly visible data is accessed by the Third-Party API Providers. ##### Why This Matters Your relationship with the Publisher is that of a software user to a software vendor. The Publisher has the responsibilities of a software vendor (functional code, accurate documentation) and the limits of one (the Publisher is not responsible for how you use the data you obtain). These Terms operate alongside but do not replace: - Apify's Terms of Service and Acceptable Use Policy (governing your relationship with Apify) - HarvestAPI Terms of Service and Scrape Creators Terms of Service (governing the underlying data infrastructure) - Source Platform terms (LinkedIn, TikTok, etc.) governing the public data accessed - Applicable law in your jurisdiction and the jurisdictions of data subjects These Terms incorporate the actor-specific addendum published in each Actor's individual listing ("Addendum"). In the event of a conflict, the more restrictive provision applies. #### 1. NATURE OF THE SERVICE ##### 1.1 What the Actor Is The Actor is a software program published on the Apify platform. Each Actor: - (a) Accepts structured input from you on the Apify platform - (b) Translates that input into HTTP requests to a third-party API operated by HarvestAPI or Scrape Creators - (c) Receives HTTP responses from that third-party API - (d) Returns the response data to you in a structured format on the Apify platform The Actor's source code is hosted on Apify's infrastructure. The Actor runs in Apify's cloud, not on the Publisher's servers. The Publisher operates no servers running the Actor. ##### 1.2 What the Actor Is Not The Actor is not: - (a) A scraping tool - the Publisher does not operate scraping infrastructure, proxies, headless browsers, or fake accounts - (b) A direct connection to any source platform - connections to source platforms are made by HarvestAPI / Scrape Creators - (c) A data storage or data retention service - the Publisher does not maintain a database of any data the Actor returns - (d) A licensed access channel to LinkedIn, TikTok, YouTube, Reddit, X (Twitter), Meta, Linktree, or any other source platform - (e) Affiliated with, endorsed by, sponsored by, or authorized by any source platform ##### 1.3 The Publisher's Limited Role The Publisher's role is limited to: - (a) Designing and writing the Actor's source code - (b) Publishing the Actor on the Apify Store - (c) Maintaining the Actor (updating it when API providers change schemas) - (d) Providing documentation and customer support via Apify's contact mechanism The Publisher is a software vendor, similar to a developer who publishes an app on the Apple App Store or Google Play Store. The Publisher is not a data provider, data broker, data processor, or data controller for purposes of GDPR, CCPA, Israel's Privacy Protection Law, or equivalent. ##### 1.4 The Third-Party API Providers' Role HarvestAPI (https://harvest-api.com) and Scrape Creators (https://scrapecreators.com) are independent third-party companies. They: - (a) Operate the actual data scraping infrastructure - (b) Maintain relationships with source platforms (or accept the operational risk of accessing public data without such relationships) - (c) Are themselves Apify publishers (HarvestAPI publishes 9+ actors directly; Scrape Creators publishes 10+) - (d) Provide their own Terms of Service governing their operations - (e) Are responsible for compliance obligations relating to the data collection itself The Publisher is a customer of these providers. The Publisher is not their agent, partner, or representative. #### 2. WHO MAY USE THE ACTOR ##### 2.1 Eligibility You may use the Actor only if: - (a) You are at least 18 years old or the age of majority in your jurisdiction - (b) You have legal capacity to enter into binding contracts - (c) You are not located in or resident of a country subject to comprehensive sanctions by the United States, European Union, United Kingdom, or Israel - (d) You are not on any prohibited persons list ##### 2.2 User Representations By using any Actor, you represent and warrant that: - (a) **Truthful identity:** Information you provide about your identity and intended use is accurate - (b) **Lawful intent:** Your intended use complies with applicable law in your jurisdiction - (c) **Source platform compliance:** You will independently comply with the Terms of Service of any source platform whose data you obtain through the Actor - (d) **Data subject rights:** Where Actor outputs include personal data, you will respect data subject rights under applicable law - (e) **No prohibited use:** You will not use the Actor for any of the purposes prohibited in Section 4 These representations are continuous - they must remain true throughout your use. #### 3. PERMITTED USES The Actor may be used for any lawful purpose, including: - Market research and competitive analysis - Academic research - Journalism and investigative reporting - Internal business intelligence - Brand monitoring - Recruitment research where consistent with applicable employment law - Building products that further process publicly available information lawfully Specific permitted uses for this Actor are described in the Addendum below. #### 4. PROHIBITED USES You may not use the Actor for any of the following: ##### 4.1 Illegal Activity Activity illegal under the law of your jurisdiction, the User's jurisdiction, or the jurisdiction of any data subjects. ##### 4.2 Harassment, Stalking, and Personal Targeting - Compiling profiles for harassment, stalking, or doxxing - Tracking individuals' movements or activities without their knowledge - Building profiles of journalists, activists, dissidents, or vulnerable populations for retaliatory purposes ##### 4.3 Discrimination - Using outputs for discriminatory employment, lending, housing, or insurance decisions based on protected characteristics - Building lists for discriminatory purposes ##### 4.4 Spam and Unsolicited Commercial Communication - Sending unsolicited marketing in violation of CAN-SPAM, CASL, GDPR, PECR, Israeli Anti-Spam Law (סעיף 30א לחוק התקשורת), or equivalent laws - Building "lead lists" from scraped contacts without proper consent infrastructure - Reselling contact data for spam purposes ##### 4.5 Fraud and Deception - Identity theft or impersonation - Generation of fake reviews, testimonials, or coordinated inauthentic behavior - Election interference or political disinformation - Securities fraud ##### 4.6 Source Platform Abuse - Using outputs to circumvent technical protection measures of source platforms - Creating fake accounts on source platforms based on Actor outputs - Vote manipulation, engagement manipulation, or platform algorithm gaming - Building services that competitively substitute for source platforms ##### 4.7 Reselling the Actor's Service - Reselling raw Actor outputs as your own data product or scraping-as-a-service - Sharing your Apify credentials to provide third parties indirect access - Building competing API services using Actor outputs ##### 4.8 AI Training Without Authorization Using Actor outputs as training data for commercial AI/ML models without separate licensing authority from the source platform. ##### 4.9 Sensitive Targeting - Specifically targeting or profiling based on health conditions, sexual orientation, religious beliefs, political opinions, or other sensitive characteristics - Targeting children under 16 (or local age of consent for data processing) ##### 4.10 Privacy Law Violations - Processing personal data of EU/UK/California/Israeli residents without complying with applicable privacy law - Failing to honor data subject access, deletion, or objection requests - Processing data for purposes incompatible with its publication context #### 5. SOURCE PLATFORM TERMS - YOUR RESPONSIBILITY ##### 5.1 Acknowledgment The Actor accesses publicly visible data on third-party platforms ("Source Platforms") through the Third-Party API Providers (HarvestAPI / Scrape Creators). Source Platforms include LinkedIn, TikTok, YouTube, Reddit, X (Twitter), Meta/Facebook, Linktree, Komi, Pillar, Linkbio, Linkme, and Amazon. ##### 5.2 Your Sole Responsibility You acknowledge: - (a) You are solely responsible for ensuring your downstream use of data obtained through the Actor complies with the Source Platform's Terms of Service - (b) The Publisher makes no representation that any specific use is permitted under any Source Platform's terms - (c) The Third-Party API Providers, not the Publisher, bear responsibility for the lawfulness of the data collection itself - (d) You should review Source Platform terms before commercial use: - LinkedIn: https://www.linkedin.com/legal/user-agreement - TikTok: https://www.tiktok.com/legal/page/global/terms-of-service/en - YouTube: https://www.youtube.com/static?template=terms - X: https://twitter.com/en/tos - Reddit: https://www.redditinc.com/policies/user-agreement - Meta: https://www.facebook.com/legal/terms - Linktree: https://linktr.ee/s/terms/ ##### 5.3 Cease-and-Desist Compliance If you receive a cease-and-desist letter or other legal demand from a Source Platform regarding your use of Actor outputs, you must: - (a) Cease the contested use immediately - (b) Notify UnseenUser within 48 hours via UnseenUser's Apify profile contact form (https://apify.com/UnseenUser) - (c) Cooperate with the Publisher as needed to mitigate - (d) Not assert against the Publisher any claim arising from your inability to use the Actor for that Source Platform #### 6. DATA PROTECTION - REFLECTING ACTUAL ARCHITECTURE ##### 6.1 Roles Under Privacy Law For purposes of GDPR, UK GDPR, CCPA, Israel's Privacy Protection Law (PPL) including Amendment 13, and equivalents: - **You (the User) are the Data Controller** of any personal data you obtain through the Actor and subsequently process for your own purposes - **HarvestAPI and Scrape Creators** are the entities that collect data from source platforms - they bear the responsibilities of data processors or controllers (depending on context) for the collection itself - **The Publisher acts solely as a software vendor**, not as a data controller or processor, because the Publisher does not store, retain, or substantively process personal data - the Actor merely passes API responses through ##### 6.2 No Data Retention by the Publisher The Publisher confirms: - (a) The Publisher does not maintain a database of personal data obtained through the Actor - (b) The Actor passes data from the Third-Party API directly to you on the Apify platform - data does not flow through the Publisher's infrastructure - (c) Apify's standard execution and operational logging may include limited information about Actor runs (input parameters, run duration, data volume) - this is governed by Apify's own privacy practices - (d) The Publisher does not access, view, or analyze your Actor outputs except as needed for technical support if you specifically share them with the Publisher ##### 6.3 Your Obligations as Data Controller Where your use of the Actor involves processing personal data, you are responsible for: - (a) Establishing a lawful basis for your processing (consent, legitimate interest with documented balancing test, contract, etc.) - (b) Providing transparent notice to data subjects as required by applicable law - (c) Honoring data subject access, rectification, erasure, restriction, and portability requests - (d) Implementing appropriate security measures - (e) Conducting Data Protection Impact Assessments where required - (f) Appointing a Data Protection Officer if your operations require one - (g) Registering databases with applicable supervisory authorities - (h) Honoring opt-out requests for direct marketing - (i) Cross-border transfer safeguards where data crosses borders ##### 6.4 Israel's Amendment 13 - User Compliance If your use of the Actor involves Israeli residents' personal data, you must comply with the Privacy Protection Law as amended (Amendment 13, effective August 14, 2025). These obligations are yours as the data controller, not the Publisher's as the software vendor. ##### 6.5 Sensitive Data Targeting Restrictions You will not use the Actor to specifically target, profile, or build datasets focused on: - Health or medical conditions - Religious beliefs - Political opinions - Sexual orientation or gender identity - Genetic or biometric data - Criminal history - Children under 16 #### 7. INTELLECTUAL PROPERTY ##### 7.1 Actor Code The Actor's source code, schemas, documentation, and branding are owned by the Publisher. You receive a limited, non-exclusive, non-transferable, revocable license to use the Actor for permitted purposes during your active subscription/run with Apify. ##### 7.2 Output Data The Publisher claims no ownership over the public data the Actor returns. Source Platforms may have copyright, database rights, or other rights in their data; data subjects may have copyright in user-generated content. Your use of output data must respect these rights independently. ##### 7.3 Restrictions You may not reverse engineer, decompile, or reuse the Actor's code in a competing actor. ##### 7.4 Feedback Feedback you provide may be used by the Publisher to improve products without compensation to you. #### 8. PRICING AND PAYMENT ##### 8.1 Apify Platform Billing Pricing is administered through Apify's pricing models. Apify processes all payments. Apify's payment terms govern refunds and disputes. ##### 8.2 Pricing Changes The Publisher may change Actor pricing with at least 14 days' notice via the Actor's Apify listing. ##### 8.3 No Refunds for Misuse If your access is suspended or terminated for breach of these Terms, you forfeit any unused balance and are not entitled to refunds. #### 9. SERVICE AVAILABILITY AND CHANGES ##### 9.1 No Uptime Guarantee The Actor depends on: - (a) The Apify platform - (b) Underlying API providers (HarvestAPI, Scrape Creators) - (c) Source Platforms' continued public accessibility Any of these may change behavior, restrict access, or become unavailable without notice. The Publisher makes no uptime guarantees. ##### 9.2 Service Discontinuation The Publisher may discontinue any Actor at any time. Reasonable notice will be provided when feasible. #### 10. DISCLAIMERS ##### 10.1 "AS IS" Service THE ACTOR IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR PURPOSE, NON-INFRINGEMENT, OR ACCURACY OF DATA. ##### 10.2 No Representation of Lawfulness The Publisher makes no representation that your specific use of the Actor or the data it returns is lawful in your jurisdiction or under any Source Platform's terms. The burden of determining lawfulness for your use case is yours. ##### 10.3 No Endorsement of Source Content Content returned by the Actor was created by third parties. The Publisher does not endorse, verify, or take responsibility for it. #### 11. LIMITATION OF LIABILITY ##### 11.1 Aggregate Liability Cap TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL THE AGGREGATE LIABILITY OF THE PUBLISHER FOR ALL CLAIMS RELATING TO THE ACTOR EXCEED THE GREATER OF: - (a) ONE HUNDRED U.S. DOLLARS (US $100), OR - (b) THE AMOUNTS YOU PAID THROUGH APIFY FOR USE OF THE ACTOR IN THE THREE (3) MONTHS IMMEDIATELY PRECEDING THE EVENT ##### 11.2 Excluded Damages THE PUBLISHER IS NOT LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOSS OF PROFITS, REVENUE, OR DATA, EVEN IF ADVISED OF THE POSSIBILITY. ##### 11.3 Time Limit Any claim must be brought within one (1) year of the event. #### 12. INDEMNIFICATION ##### 12.1 Your Indemnification of the Publisher You agree to defend, indemnify, and hold harmless the Publisher from any: - Claims arising from your use of the Actor - Claims arising from your violation of these Terms - Claims arising from your violation of any law (including privacy law) - Claims arising from your violation of any Source Platform's Terms of Service - Claims arising from your processing of personal data obtained through the Actor - Reasonable attorneys' fees and costs of defending such claims ##### 12.2 Defense The Publisher may assume defense at your expense. You will cooperate with the Publisher's defense. ##### 12.3 Scope The indemnification covers reasonable, foreseeable third-party claims arising from your use. It does not extend to: - Claims arising from the Publisher's gross negligence or willful misconduct - Claims regarding the Actor's source code itself (those are the Publisher's responsibility) - Claims regarding the Third-Party API Provider's data collection (those are their responsibility) #### 13. SUSPENSION AND TERMINATION ##### 13.1 Termination by the Publisher The Publisher may terminate your access for material breach, illegal use, breach of warranty, or upon credible legal demand. ##### 13.2 Effects of Termination Your license ends, you must cease use, and applicable provisions survive. ##### 13.3 Termination by You You may stop using the Actor at any time on Apify. #### 14. DISPUTE RESOLUTION ##### 14.1 Informal Resolution First Send a detailed written description of the dispute via UnseenUser's Apify profile contact form (https://apify.com/UnseenUser) and wait 60 days for resolution attempt before any formal claim. ##### 14.2 Governing Law These Terms are governed by the substantive laws of the State of Israel, without regard to conflict of law principles. ##### 14.3 Exclusive Jurisdiction Any dispute shall be brought exclusively in the competent civil courts of Tel Aviv-Jaffa, Israel. ##### 14.4 No Class Actions You agree to bring claims only in your individual capacity. ##### 14.5 Attorneys' Fees The prevailing party recovers reasonable attorneys' fees. #### 15. MISCELLANEOUS - **15.1 Entire Agreement** - These Terms (with Addendum and incorporated documents) are the entire agreement. - **15.2 Severability** - Unenforceable provisions are reformed to the minimum extent or severed. - **15.3 Assignment** - You may not assign without the Publisher's consent. The Publisher may assign to affiliates, successors, or acquirers. - **15.4 Force Majeure** - Neither party is liable for failure due to events beyond reasonable control, including changes by Source Platforms or Third-Party API Providers, or actions by Apify. - **15.5 Third-Party Beneficiaries** - Apify, HarvestAPI, and Scrape Creators are intended third-party beneficiaries of Sections 4 (Prohibited Uses), 5 (Source Platform Compliance), and 12 (Indemnification). - **15.6 Survival** - Sections 0 (Acceptance), 4, 5, 6, 7, 10, 11, 12, 14, and 15 survive termination. - **15.7 Language** - English controls. Translations are for convenience only. - **15.8 Publisher Identification for Legal Process** - The Publisher operates on the Apify platform under the username UnseenUser (https://apify.com/UnseenUser). The Publisher is a registered legal entity. Upon receipt of valid legal process (subpoena, court order, or equivalent) directed through Apify's official channels, the Publisher's full legal identity may be disclosed as required by law. #### 16. ACKNOWLEDGMENT By using any Actor, you acknowledge that: - (a) You have read these Terms - (b) You understand the architecture: you are using software (the Actor) on Apify's platform that calls third-party APIs - (c) You accept responsibility for your use, including for compliance with Source Platform terms - (d) Your indemnification obligations cover third-party claims arising from your use - (e) Disputes are resolved in Israeli courts - (f) The Publisher's identity, while not publicly disclosed in this listing, can be obtained through valid legal process via Apify For questions, use UnseenUser's Apify profile contact form (https://apify.com/UnseenUser) before running the Actor. *** ### 🛡️ Actor-Specific ToS Addendum - 🏢 LinkedIn Company + Posts Scraper This addendum supplements the Master Terms of Service V4.0 above. By running this Actor, you accept both the Master ToS and this addendum. #### A. Architectural Disclosure This Actor is a software wrapper. It accepts your input parameters, calls **TWO HarvestAPI endpoints in sequence** (`/linkedin/company` + `/linkedin/company-posts`), combines the results into a structured output, and returns the combined data to you on the Apify platform. UnseenUser does not store, log, or substantively process the data returned. The data flows from HarvestAPI through Apify's runtime directly to you. #### B. Nature of Data Returned This Actor returns: Full LinkedIn company profile (name, tagline, website, founded date, employee count, follower count, headquarter, industries, specialities, funding data from Crunchbase) + all company posts (text, images, video URLs, articles, polls, reposts, engagement metrics with reaction breakdowns). Where the Actor's output includes individual people's names, photos, contact details, or content authored by them, that data constitutes personal data subject to GDPR, CCPA, Israeli Privacy Protection Law, and equivalent privacy laws in your downstream processing - but only in your hands as the data controller, not in UnseenUser's hands as the software vendor. #### C. Permitted Use Cases You may use this Actor for the following purposes (non-exhaustive list): - **Account-based research** - get one CSV row per target account with profile + recent posts - **Competitive monitoring** - track competitor company info changes alongside posting activity - **Sales enablement** - equip reps with full company profile + their latest LinkedIn content before calls - **Investor due diligence** - research a target company's public positioning, headcount, funding, and content cadence - **Content marketing benchmarking** - see what topics industry leaders post about and how often - **Lead enrichment** - enrich CRM accounts with the deepest available LinkedIn data per company - **Brand monitoring** - detect mentions, tone shifts, or crisis posts on competitor pages #### D. Specifically Prohibited Uses In addition to Master ToS Section 4 prohibitions, you may NOT: - Republish full posts in commercial products that compete with LinkedIn - Use post content to train commercial AI/LLMs without complying with LinkedIn's data use terms - LinkedIn's User Agreement explicitly restricts this - Build engagement-bait systems that copy successful post patterns and impersonate companies - Mass-DM employees of scraped companies without complying with anti-spam laws - Resell company funding data as a substitute for Crunchbase, PitchBook, or similar paid services - Aggregate this data with personal data to build comprehensive 'company intelligence dossiers' covering named employees - Use post sentiment to short-sell or short-trade against companies based on automated content analysis (market manipulation exposure) #### E. Platform Terms of Service Considerations LinkedIn has actively litigated against profile/company scrapers (LinkedIn v. Proxycurl 2025, LinkedIn v. ProAPIs 2025-2026, hiQ Labs v. LinkedIn). LinkedIn's User Agreement explicitly prohibits automated extraction. This Actor accesses publicly visible LinkedIn company data via HarvestAPI - HarvestAPI bears responsibility for the lawfulness of the data collection. Your downstream use must independently comply with LinkedIn's Terms of Service. If LinkedIn issues a cease-and-desist regarding data obtained via this Actor, notify UnseenUser within 48 hours via the Apify profile contact form (https://apify.com/UnseenUser). #### F. Combined-Endpoint Data Sensitivity This Actor combines two endpoints in one run. The combination yields data that is **MORE sensitive than either endpoint alone**: - **Company profile alone:** low sensitivity (factual business info) - **Posts alone:** medium sensitivity (creator copyright, employee personal data in some posts) - **Combined:** enables building a complete "company intelligence dossier" with structured profile + behavioral content data This combined view is the kind of dataset that LinkedIn specifically targets in their lawsuits. Use the combined output thoughtfully: - Don't sell the combined dataset as a product - Don't build a "LinkedIn replacement" with this data - Use it for your own internal research/enrichment #### G. Post Author Copyright Each post is copyrighted by its author (the company or the individual posting on behalf of the company). You may use posts for: - Analysis and research (typically fair use) - Quotation with attribution (typically fair use) - Aggregated metrics (no copyright issue - facts aren't copyrightable) You may **NOT**: - Republish full posts in commercial products without licensing - Use posts to train commercial AI without proper licensing - Translate and republish without authorization - Build a "LinkedIn posts search engine" using this data #### H. Crunchbase Funding Data The company profile includes funding data sourced from Crunchbase via LinkedIn. This is: - Generally factual public information - Subject to Crunchbase's terms of service indirectly - Not authoritative - verify with official sources for material decisions - May lag behind real-time announcements If you redistribute this funding data, attribute the original source (Crunchbase) where possible. #### I. Employee Personal Data in Posts Company posts often include: - Names and photos of employees - Job announcements with new-hire info - Bereavement, illness, layoff disclosures - Celebrity employee mentions Treat these as personal data in your downstream processing. Do not use sensitive disclosures (layoffs, illness, bereavement) to identify vulnerable people for commercial targeting - this is explicitly prohibited under Section 4 of the Master ToS. #### J. Content Freshness The two endpoints have different freshness characteristics: - `/linkedin/company` data is relatively stable (changes when companies update their pages) - `/linkedin/company-posts` data is real-time (changes constantly) When you store the combined output, timestamp BOTH parts separately. Treating outdated profile data as current can lead to material business decisions based on stale information. *** ### Related scrapers Build a complete LinkedIn intelligence stack: - [LinkedIn Company Scraper Pro](https://apify.com/unseenuser/LinkedIn-Company-Scraper) - company data only (cheaper if you don't need posts) - [LinkedIn Profile Scraper + Email Enrichment](https://apify.com/unseenuser/LinkedIn-Profile) - enrich people at these companies - [LinkedIn Jobs Scraper](https://apify.com/unseenuser/LinkedIn-Jobs-Scraper) - see who they're hiring (intent signal) [See all 18 scrapers by unseenuser](https://apify.com/unseenuser) *** ### Keywords linkedin company posts scraper, linkedin company data api, scrape linkedin company, linkedin company intel, linkedin firmographics api, linkedin company posts, linkedin abm tool, company content monitoring, b2b research automation # Actor input Schema ## `companyUrls` (type: `array`): Paste one or more LinkedIn company URLs. Posts from each page will appear as rows in the output. Example: https://www.linkedin.com/company/google ## `max_posts` (type: `integer`): Number of posts to scrape per company. Set to 0 to fetch every available post. Default 100. ## `date_filter` (type: `string`): Only return posts published within this time window. ## Actor input object example ```json { "companyUrls": [ "https://www.linkedin.com/company/google" ], "max_posts": 100, "date_filter": "" } ``` # Actor output Schema ## `dataset` (type: `string`): Primary output. One row per company URL with the LinkedIn company profile, the array of posts collected, per-row metadata, and an optional error object that includes a human-readable 'fix' field. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "companyUrls": [ "https://www.linkedin.com/company/google" ] }; // Run the Actor and wait for it to finish const run = await client.actor("unseenuser/company-posts").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "companyUrls": ["https://www.linkedin.com/company/google"] } # Run the Actor and wait for it to finish run = client.actor("unseenuser/company-posts").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "companyUrls": [ "https://www.linkedin.com/company/google" ] }' | apify call unseenuser/company-posts --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=unseenuser/company-posts", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "LinkedIn Company Posts Scraper [NO COOKIES] ✅", "description": "Scrape a LinkedIn company's all recent posts in one run. Get full post text, engagement, and posting cadence. No login, no cookies. Built for ABM, competitive intel, and content strategy teams.", "version": "0.0", "x-build-id": "td12VMHH42m9pH3QA" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/unseenuser~company-posts/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-unseenuser-company-posts", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/unseenuser~company-posts/runs": { "post": { "operationId": "runs-sync-unseenuser-company-posts", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/unseenuser~company-posts/run-sync": { "post": { "operationId": "run-sync-unseenuser-company-posts", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "properties": { "companyUrls": { "title": "LinkedIn company URLs", "type": "array", "description": "Paste one or more LinkedIn company URLs. Posts from each page will appear as rows in the output. Example: https://www.linkedin.com/company/google", "items": { "type": "string" } }, "max_posts": { "title": "How many posts to fetch per company (0 = all)", "minimum": 0, "maximum": 1000, "type": "integer", "description": "Number of posts to scrape per company. Set to 0 to fetch every available post. Default 100.", "default": 100 }, "date_filter": { "title": "Posted within", "enum": [ "", "1h", "24h", "week", "month", "3months", "6months", "year" ], "type": "string", "description": "Only return posts published within this time window.", "default": "" } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```