Skip to main content
POST
/
actions
/
linkedin-extract-salesnavigator-profile-id
/
run
/
async
Run linkedin-extract-salesnavigator-profile-id action asynchronously
curl --request POST \
  --url https://api.edges.run/v1/actions/linkedin-extract-salesnavigator-profile-id/run/async \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "inputs": [
    {
      "linkedin_profile_url": "<string>",
      "custom_data": {}
    }
  ],
  "name": "<string>",
  "identity_ids": [
    "44444444-4444-4444-4444-444444444444"
  ],
  "identity_mode": "direct"
}
'
{
  "run_id": 123,
  "run_uid": "<string>",
  "workspace_uid": "<string>",
  "user_uid": "<string>",
  "action_name": "<string>",
  "postponed_until": "2023-11-07T05:31:56Z",
  "created_at": "2023-11-07T05:31:56Z",
  "updated_at": "2023-11-07T05:31:56Z",
  "name": "<string>"
}

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.
Callback Delivery: Both async and schedule modes deliver results via the callback URL provided in your request.Consistent Format: All execution modes use the same action logic, so inputs and results are identical regardless of mode.Error Handling: Errors follow the standard API error format.
Using async and schedule modes, you have to implement some kind of callback management. Be sure to check the Managing Callbacks guide to better understand how it works and what your can do.

Authorizations

​
X-API-Key
string
header
required

Body

application/json
​
inputs
object[]
required
Required array length: 1 - 100000 elements
​
name
string | null

Optional user-defined label for the run.

Maximum string length: 255
​
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
​
callback
object

Callbacks

POST
{$request.body#/callback/url}onSave

Body

application/json
​
callback_ref_uid
string<uuid>
required

Stable callback identifier (remains identical across retries). Used by clients for deduplication.

​
run
object
required
​
input
object
​
error
APIError · object

Represents an error returned by the API. This schema defines the standard structure of error messages to ensure consistent error handling across the application.

​
results_count
integer

Number of results included in this callback.

​
results
object[]

Results of the current callback

Response

200

Callback successfully processed

Response

Default Response

​
run_id
integer

The ID of the run.

​
run_uid
string

The UID of the run.

​
workspace_uid
string

The UID of the workspace.

​
user_uid
string

The UID of the user.

​
action_name
string

The name of the action.

​
status
enum<string>

The status of the run.

Available options:
pending,
running,
completed,
failed
​
postponed_until
string<date-time> | null

If the run is postponed, this field indicates when it will be retried.

​
created_at
string<date-time>

The date and time when the run was created.

​
updated_at
string<date-time> | null

The date and time when the run was last updated.

​
name
string | null

Optional user-defined label for the flow run.

Maximum string length: 255