Skip to main content
POST
/
actions
/
linkedin-extract-salesnavigator-profile-id
/
run
/
live
Run linkedin-extract-salesnavigator-profile-id action live
curl --request POST \
  --url https://api.edges.run/v1/actions/linkedin-extract-salesnavigator-profile-id/run/live \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "input": {
    "linkedin_profile_url": "<string>",
    "custom_data": {}
  },
  "identity_ids": [
    "44444444-4444-4444-4444-444444444444"
  ],
  "identity_mode": "direct"
}
'
{ "linkedin_profile_id": null, "sales_navigator_profile_id": null, "linkedin_profile_handle": "", "linkedin_profile_url": null, "sales_navigator_profile_url": null }

Documentation Index

Fetch the complete documentation index at: https://docs.edges.run/llms.txt

Use this file to discover all available pages before exploring further.

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.

​
Notes

Resolve a Sales Navigator profile ID from a LinkedIn profile identifier. Input (one of):
  • linkedin_profile_handle
  • linkedin_profile_url
Output highlights: sales_navigator_profile_id, sales_navigator_profile_url, linkedin_profile_handle, linkedin_profile_url, linkedin_profile_id
  • The returned sales_navigator_profile_id is always an ACo, even if a Sales Navigator URL in the input used another ID format.
  • If the LinkedIn handle or profile does not exist, the API returns STATUS_404.

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.

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

​
linkedin_profile_id
integer
​
sales_navigator_profile_id
string
​
linkedin_profile_handle
string
default:""
​
linkedin_profile_url
string<uri>
​
sales_navigator_profile_url
string<uri>