Skip to main content
POST
Run salesnavigator-search-people action live
1 credit per result · credit_ratio 1 · Credit costs Sales Navigator people search 950 / 24 h · Action limits

Agent skill

edges-salesnavigator-search-people — ready-made instructions for coding agents calling this endpoint.
One page of results costs one call against the quota. A page holds 25 profiles, so 100 results consume 4 calls, not 100. Pagination is what draws down this action’s allowance — not the number of records you end up with.
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 to run without connecting an account.
Prefer X-Pagination-Next and X-Pagination-Previous over constructing pagination URLs yourself. Stop only when X-Pagination-Next is absent — a short page (fewer results than the previous page, or than the action’s usual page size) does not mean you are done. LinkedIn’s page length can vary from one request to the next; the result array length is not a stop condition.
If you are looking for the “saved search” version of this action, use the Saved Search Sales Navigator People endpoint instead.

Authorizations

X-API-Key
string
header
required

Query Parameters

cursor
string

Cursor value obtained from the X-Pagination-Next response header of a previous request, used to continue pagination. Cursors expire after 24 hours. If a cursor has expired or is invalid, pagination must be restarted from the beginning.

page_size
integer
default:25

Maximum number of results per page (read-only; defined by the endpoint, actual count may be lower in some cases like throttling or internal limits).

Required range: 25 <= x <= 25

Body

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

Example:
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

full_name
string
first_name
string
last_name
string
company_name
string
sales_navigator_company_id
string
linkedin_profile_id
integer
connection_degree
integer
job_title
string
summary
string
profile_image_url
string<string>
sales_navigator_search_url
string<string>
sales_navigator_profile_url
string<string>
linkedin_profile_url
string<string>
sales_navigator_profile_id
string
sales_navigator_company_url
string<string>
location
string
linkedin_people_post_search_url
string<string>
viewed
boolean
tenure_start
string
tenure_end
string
tenure_length
string
recently_hired
boolean
recently_promoted
boolean
current_company
string