LinkedIn Post likes
Get the list of people who liked or reacted to a post
Endpoint
One endpoint for every offer below. Omit provider and the router picks with automatic failover — the response's served_by tells you which one ran.
https://api.socialrouter.io/v1/extract/linkedin/post.likesOffers
Every offer below returns the same normalized output, in failover order — the first one serves unless you pin another with the provider field.
apify/apimaestrovia Apifydefault routeUp to 1000 URLs per request
$0.0069per record
Parameters
JSON body of the request. Unknown fields and unknown options are rejected with the valid list, so a wrong guess costs nothing.
| Parameter | Type | Description |
|---|---|---|
urlsRequired | string[] | One URL per record to process. Accepted shapes:https://www.linkedin.com/posts/<slug>-activity-<id>-<suffix> — The URL must contain the numeric activity ID.<activity_id> (raw numeric ID)Example: https://www.linkedin.com/posts/satyanadella_ai-activity-7123456789012345678-AbCdA single url string is accepted too. |
providerOptional | string | Pin one offer, e.g. apify/apimaestro. Omit it and the router picks with failover. |
limitOptional | integer | Max records to return per URL. |
Output
Each record has the fields below, whichever offer serves the request. Offers may include additional platform-specific fields on top.
namestringFull name of the person who liked the post
profile_urlurlLink to the liker's public profile
headlinestringHeadline or bio shown next to their name (when available)
reaction_typestringType of reaction ("like", "love", "insightful", …)
sourcestringPlatform the record was extracted from (e.g. "linkedin")
extracted_atiso8601UTC timestamp when the record was produced
Going further
Auth, error semantics, and every other endpoint live in the API reference — including the machine-readable OpenAPI spec at /v1/openapi.json.
Frequently asked questions
How much does LinkedIn post likes cost?
Prices start at $0.0069 per record, depending on the offer that serves the request. You are only charged for records actually returned.
Which offers serve linkedin/post.likes?
apify/apimaestro — 1 offer is available behind the same endpoint. Pin one with the optional "provider" field, or omit it and the router picks with automatic failover. The response's "served_by" field names the offer that ran.
What input does it need?
The "urls" field of the JSON body, as an array of strings: https://www.linkedin.com/posts/<slug>-activity-<id>-<suffix> — The URL must contain the numeric activity ID.; or <activity_id> (raw numeric ID). For example: https://www.linkedin.com/posts/satyanadella_ai-activity-7123456789012345678-AbCd
Is the output format the same for every offer?
Yes. Every offer returns the normalized record schema documented on this page; some add extra platform-specific fields on top, but the documented fields are always present.
How many URLs can I send per request?
Up to 1000 URLs in a single request, depending on the offer.
What happens if an offer fails?
SocialRouter automatically fails over to the next offer serving the same service, so a single upstream outage doesn't break your integration.