LinkedIn Post Engagers
Everyone who reacted to or commented on a LinkedIn post, matched to the Lead Database for their work email, title and company. Paste up to 25 post links, or give a keyword and we read the reactions and comments on the posts it finds. One row per person (someone on several of the posts is one row, with how many they engaged with): name, headline, profile URL, reaction type, comment text, current title, company and location, plus the work email and company website when the Lead Database holds them. People with a work email come first.
POST /api/v1/scrape/linkedin-post-engagersParameters
| Name | Type | Required | Description |
|---|---|---|---|
postUrls | string[] | Optional | LinkedIn post links (linkedin.com/posts/... or linkedin.com/feed/update/urn:li:activity:...), up to 25. Give this or keyword.Example: ["https://www.linkedin.com/posts/..."] |
keyword | string | Optional | Instead of links: a keyword; the posts LinkedIn search finds for it are read. Give this or postUrls.Example: cold email |
postedWithin | string | Optional | With keyword: how recent the posts are. 24h, week, month, 3months, 6months, year or any.Default: monthExample: month |
maxPosts | number | Optional | With keyword: how many posts to read (1 to 50)Default: 10Example: 10 |
engagement | string | Optional | all (everyone who reacted or commented), reactions or commentsDefault: allExample: all |
maxPerPost | number | Optional | The most people read from each post (1 to 3,000)Default: 1000Example: 1000 |
maxEngagers | number | Optional | The most people returned for the whole search (1 to 5,000). People who commented are read first, then people who reacted.Default: 500Example: 500 |
Examples
Everyone who engaged with two posts
curl -X POST https://app.scrapercity.com/api/v1/scrape/linkedin-post-engagers \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"postUrls": [
"https://www.linkedin.com/posts/POST-ONE",
"https://www.linkedin.com/posts/POST-TWO"
],
"maxEngagers": 500
}'People commenting on this month's posts about a topic
curl -X POST https://app.scrapercity.com/api/v1/scrape/linkedin-post-engagers \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"keyword": "cold email",
"postedWithin": "month",
"maxPosts": 10,
"engagement": "comments",
"maxEngagers": 1000
}'Check status and download
curl -X GET https://app.scrapercity.com/api/v1/scrape/status/{runId} \
-H "Authorization: Bearer YOUR_API_KEY"
# When status is SUCCEEDED, download the CSV
curl -L https://app.scrapercity.com/api/downloads/{runId} -o post-engagers.csvUse Cases
- •Reach the people engaging with a competitor's launch or an influencer in your market while the topic is fresh
- •Follow up with everyone who reacted to or commented on your own posts
- •Build a list of people talking about a topic this week from a keyword
- •Find warm prospects for outbound: people who engaged are active on LinkedIn and care about the subject
Best Practices
- •Charged per person returned, with a minimum charge per search; a person on several of the posts is charged once
- •Most searches finish in 2 to 20 minutes; a search of thousands of reactions can take longer
- •In our tests on posts about B2B software about 1 in 4 people were in the Lead Database and about 1 in 7 came with a work email; everyone comes with their name, headline and profile link, and people who reacted with their current title, company and location
- •CSV columns: full_name, first_name, last_name, headline, linkedin_url, engagement, reaction_type, comment, posts_engaged, post_url, title, company_name, company_domain, company_linkedin, company_industry, company_size, city, state, country, email, email_status, in_lead_database
Every scrape returns a runId. Poll GET /api/v1/scrape/status/{runId} until it completes, then download via GET /api/downloads/{runId}?format=csv.
Authenticate every request with Authorization: Bearer YOUR_API_KEY. See the full API reference for authentication, rate limits and error codes.