Use LinkedIn Post Reactor Identity & Reaction Type Scraper with Python

Scrape the reactors on LinkedIn posts with name, headline, profile URL, and the specific reaction type they left, filterable by reaction type and date using your own LinkedIn session.

1. Choose the data you need

Review the published README for supported collection modes, examples, and limits. The recipe below uses the current published input definition.

2. Prepare a source-based input

This JSON contains published prefills and required-field defaults. Review every value for your task before running it; it is not a promise of successful collection.

{
  "emitNoResultsMarker": true,
  "postUrls": [
    "https://www.linkedin.com/posts/microsoft_this-month-the-microsoft-atlanta-team-in-activity-7516505833061474305-T6ou"
  ],
  "reactionTypeFilter": []
}

Download input.example.json and save your reviewed copy as input.json.

3. Start an Actor run

Set APIFY_TOKEN in your environment. Python 3.10 or newer is sufficient; this recipe uses no third-party packages.

Execution may incur charges. Review current pricing on Apify. The request asks for a 120-second timeout and a charge limit; these settings are subject to Apify’s pricing and do not guarantee an all-inclusive spending cap.

import json
import os
import urllib.request

# Save the schema-derived example as input.json; review and edit it first.
with open("input.json", encoding="utf-8") as stream:
    actor_input = json.load(stream)

token = os.environ["APIFY_TOKEN"]
request = urllib.request.Request(
    "https://api.apify.com/v2/acts/NvggfHSdNu8V6APDG/runs?timeout=120&maxTotalChargeUsd=0.50",
    data=json.dumps(actor_input).encode("utf-8"),
    headers={"Authorization": "Bearer " + token, "Content-Type": "application/json"},
    method="POST",
)
# This starts a potentially billable run. Do not automatically retry this POST.
with urllib.request.urlopen(request, timeout=40) as response:
    run = json.load(response)["data"]
print("Run ID:", run["id"])
print("Status:", run["status"])
# Inspect and download results in Apify Console once the run succeeds.

4. Inspect the actual results

Open the run in Apify Console and wait for a successful completion. Use the published output schema to locate results and the dataset schema to understand declared views. Missing or optional record fields must not be treated as guaranteed values.

One record per public post: total reactions, exact counts for like/celebrate/love/support/insightful/funny/superLike when LinkedIn's guest layout exposes them, reaction types present, optional comment/repost totals, post URL and timestamp. Reactor identities are not returned.

Questions before you run

Generated from source build I1DCTvghEDiSJaPvW and its README and schemas. Source changes regenerate this guide; no third-party editorial claims are inferred.