Skip to main content
POST
/
actions
/
linkedin-extract-contact
/
run
/
live
Run linkedin-extract-contact action live
curl --request POST \
  --url https://api.edges.run/v1/actions/linkedin-extract-contact/run/live \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '{
  "identity_ids": [
    "3c90c3cc-0d44-4b50-8888-8dd25736052a"
  ],
  "identity_mode": "direct",
  "input": {
    "linkedin_profile_url": "<string>",
    "custom_data": {}
  }
}'
{
  "connected_at": "2023-11-07T05:31:56Z",
  "email": "jsmith@example.com",
  "website": "<string>",
  "twitter_handles": [
    "<string>"
  ],
  "linkedin_profile_handle": "<string>",
  "linkedin_profile_url": "<string>",
  "twitter": "<string>",
  "phones": [
    "<string>"
  ],
  "phone": "<string>",
  "sales_navigator_profile_id": "<string>",
  "linkedin_profile_id": 123
}
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.

Authorizations

​
X-API-Key
string
header
required

Body

application/json
​
input
object
required
​
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

​
connected_at
string<date-time>
​
email
string<email>
​
website
string<uri>
​
twitter_handles
string[]
​
linkedin_profile_handle
string
​
linkedin_profile_url
string<uri>
​
twitter
string<uri>
​
phones
string[]
​
phone
string
​
sales_navigator_profile_id
string
​
linkedin_profile_id
integer
⌘I