LinkedIn Post Engagers
Up to 100 people who reacted to or commented on a public LinkedIn post.
curl -X POST https://api.1lookup.dev/v1/linkedin-post-engagers \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://www.linkedin.com/posts/northwind-example_activity-7200000000000000000"}'{
"success": true,
"data": {
"post_url": "https://www.linkedin.com/posts/northwind-example_activity-7200000000000000000",
"engagers": [
{
"name": "Jordan Avery",
"headline": "Head of Revenue Operations at Fabrikam Health",
"profile_url": "https://www.linkedin.com/in/jordan-avery-example",
"engagement_type": "reaction",
"reaction_type": "like",
"comment_text": null
},
{
"name": "Priya Raman",
"headline": "Operations Director at Contoso Roasters",
"profile_url": "https://www.linkedin.com/in/priya-raman-example",
"engagement_type": "comment",
"reaction_type": null,
"comment_text": "We moved our office coffee to a subscription last year. Curious how you handle delivery windows."
},
{
"name": "Marcus Bell",
"headline": "Procurement Manager at Northwind Logistics",
"profile_url": "https://www.linkedin.com/in/marcus-bell-example",
"engagement_type": "reaction",
"reaction_type": "celebrate",
"comment_text": null
}
]
},
"meta": {
"credits_used": 5,
"credits_remaining": 999,
"cached": false,
"request_id": "req_8f3a2c1e9b7d"
}
}Authorization
Authorizationstring<bearer>requiredYour API key as a Bearer token. Live keys start with 1lk_live_. Test keys start with 1lk_test_ and return this endpoint's sample response without spending credits. See authentication.
Body
Send the fields as a JSON object with Content-Type: application/json.
urlstring<uri>requiredLinkedIn post URL. Example: https://www.linkedin.com/posts/northwind-example_activity-7200000000000000000
freshbooleanSkip the 7-day cache and run a new lookup. Charged as a normal lookup.
referencestringYour own identifier, echoed back in meta and shown in lookup history.
Response
A 200 response carries the result in data and the cost of the call in meta. These are the fields most integrations read.
successbooleantrue when the lookup ran.
data.post_urlstringThe LinkedIn post the list was built from.
data.engagers[].namevalueThe person's name as shown on LinkedIn.
data.engagers[].headlinevalueTheir LinkedIn headline, which usually states a role and a company.
data.engagers[].profile_urlvalueA link to the person's public LinkedIn profile.
data.engagers[].engagement_typevalueWhether the person reacted or commented.
data.engagers[].reaction_typevalueThe reaction they chose, such as like or celebrate. Null for comments.
data.engagers[].comment_textvalueWhat they wrote, when the engagement is a comment. Null for reactions.
meta.credits_usednumberCredits charged for this call.
meta.credits_remainingnumberYour balance after the call.
meta.cachedbooleantrue when the result came from the 7-day cache.
meta.request_idstringQuote this when you contact support.
Errors
A failed request returns success: false with an error object, and is never charged. The full list is on the errors page.
| HTTP | Code | Meaning |
|---|---|---|
| 401 | unauthorized | The key is missing, malformed or revoked. |
| 402 | insufficient_credits | Your credits are used up and pay as you go is off or at its limit. |
| 422 | invalid_input | A field is missing or malformed. The field property names it. |
| 429 | rate_limited | Too many requests for this key. Wait for the Retry-After interval. |
| 500 | internal_error | Something failed on our side. Safe to retry. |
| 503 | source_unavailable | An upstream source did not answer in time. Safe to retry. |
Billing
5 credits / post. Charged when the lookup runs and returns a result. Errors are never charged, and repeating the same input within 7 days is served from cache at no charge.
Product overview and use cases