Skip to main content
POST
/
actions
/
linkedin-extract-profile-viewers
/
run
/
live
Run linkedin-extract-profile-viewers action live
curl --request POST \
  --url https://api.edges.run/v1/actions/linkedin-extract-profile-viewers/run/live \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '{
  "parameters": {},
  "identity_ids": [
    "3c90c3cc-0d44-4b50-8888-8dd25736052a"
  ],
  "identity_mode": "direct"
}'
[
  {
    "view_timestamp": 123,
    "view_date": "2023-11-07T05:31:56Z",
    "connection_degree": "<string>",
    "linkedin_profile_handle": "<string>",
    "headline": "<string>",
    "linkedin_profile_url": "<string>",
    "sales_navigator_profile_id": "<string>",
    "linkedin_profile_id": 123,
    "profile_image_url": "<string>",
    "linkedin_people_post_search_url": "<string>"
  }
]
To run LinkedIn actions, you must first create an identity and connect a LinkedIn account, either using our Chrome Extension, username/password login, or Rented 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:10

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: 10 <= x <= 10

Body

application/json
​
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.

​
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

​
view_timestamp
integer
​
view_date
string<date-time>
​
connection_degree
string
​
linkedin_profile_handle
string
​
headline
string
​
linkedin_profile_url
string<uri>
​
sales_navigator_profile_id
string
​
linkedin_profile_id
integer
​
profile_image_url
string<uri>
​
linkedin_people_post_search_url
string<uri>
⌘I