Skip to main content
POST
/
actions
/
salesnavigator-search-saved-people
/
run
/
async
Run salesnavigator-search-saved-people action asynchronously
curl --request POST \
  --url https://api.edges.run/v1/actions/salesnavigator-search-saved-people/run/async \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "inputs": [
    {
      "sales_navigator_profile_search_url": "<string>",
      "custom_data": {}
    }
  ],
  "parameters": {},
  "name": "<string>",
  "identity_ids": [
    "44444444-4444-4444-4444-444444444444"
  ]
}
'
{
  "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.

Sales Navigator allows users to save searches for people and companies they are interested in. These saved searches are specific to each LinkedIn account and can be reused for future searches. More on this in the LinkedIn help center.
If your Sales Navigator search url contains a savedSearchId parameter, it indicates that the search is a saved search.
Note that these actions do not use the common search limits, which may allow you to perform more calls.
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.
Async action calls automatically handle pagination through the X-AUTO-PAGINATE header, iterating over all pages of results and sending batches to your callback URL. You can limit the total number of results with the parameters.max_results param (see “Body” section).
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
​
parameters
object
​
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"]
​
callback
object

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