Skip to main content
POST
/
actions
/
linkedin-extract-post-likers
/
run
/
live
Run linkedin-extract-post-likers action live
curl --request POST \
  --url https://api.edges.run/v1/actions/linkedin-extract-post-likers/run/live \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "input": {
    "linkedin_post_url": "<string>",
    "custom_data": {}
  },
  "parameters": {},
  "identity_ids": [
    "44444444-4444-4444-4444-444444444444"
  ],
  "identity_mode": "direct"
}
'
[
  {
    "full_name": "<string>",
    "first_name": "<string>",
    "last_name": "<string>",
    "reaction_type": "<string>",
    "reaction_urn": "<string>",
    "linkedin_profile_url": "<string>",
    "liker_connection_degree": "<string>",
    "sales_navigator_profile_id": "<string>",
    "sales_navigator_profile_url": "<string>",
    "job_title": "<string>",
    "linkedin_profile_id": 123,
    "linkedin_people_post_search_url": "<string>",
    "linkedin_post_url": "<string>",
    "linkedin_post_id": "<string>"
  }
]
This action allows you to extract users who liked a LinkedIn post.
The public handle (e.g., john-doe) is not returned in the response. The linkedin_profile_url field contains a different identifier format. If you need the real public profile URL, you’ll need to enrich the extracted people using the Extract LinkedIn People action.

​
Sorting behavior

The Most relevant sorting option intentionally hides part of the data (this is a LinkedIn limitation we cannot control). For example, a post with 1,500 potential likers may only return around 400 results with this sorting.
The Newest sorting option may sometimes return incomplete pages, but it will return the complete dataset. For example, all 1,500 likers will be extracted even if some pages have fewer results than expected.
We recommend using the Newest sorting option if you need to extract all likers from a post.

​
Misc

To run LinkedIn actions, you must first create an identity and connect a LinkedIn account, either using our Chrome Extension, username/password login, or Managed Accounts for a hassle-free setup.
X-Pagination-Next and X-Pagination-Previous headers may be included in the response to provide full URLs for the next or previous pages. When present, always prefer using these headers over manually constructing pagination URLs.

Authorizations

​
X-API-Key
string
header
required

Query Parameters

​
page
integer
default:1

Page index for manual pagination, starting at 1; increase sequentially (page=1, page=2, etc.) until the response returns an empty data array.

​
page_size
integer
default:30

Maximum number of results per page (read-only; defined by the Action, actual count may be lower in some cases like throttling or internal limits).

Required range: 30 <= x <= 30

Body

application/json
​
input
object
required
​
parameters
object
​
identity_ids
string<uuid>[] | null

An array of Identity UUIDs linked to identities (e.g. LinkedIn) used to execute the Action. You must provide at least one valid UID with access to the integration. Do not use account_uid values — only user_uid is supported.

Example:
["44444444-4444-4444-4444-444444444444"]
​
identity_mode
enum<string> | null
default:direct

If "auto", the Action will use any identities from the current workspace (unless you have provided a list of identity_ids). "managed" will use the Edges pool of identities for an extra credit cost

Available options:
direct,
auto,
managed

Response

Successful response

​
full_name
string
​
first_name
string
​
last_name
string
​
reaction_type
string
​
reaction_urn
string
​
linkedin_profile_url
string<uri>
​
liker_connection_degree
string
​
sales_navigator_profile_id
string
​
sales_navigator_profile_url
string<uri>
​
job_title
string
​
linkedin_profile_id
integer
​
linkedin_people_post_search_url
string<uri>
​
linkedin_post_url
string<uri>
​
linkedin_post_id
string