Skip to main content
POST
Run linkedin-search-people action live
1 credit per result · credit_ratio 1 · Credit costs People search 450 / 24 h · Unique people returned by search 900 / 24 h · Action limits

Agent skill

edges-linkedin-search-people — ready-made instructions for coding agents calling this endpoint.
LinkedIn’s own monthly cap. Accounts without a Sales Navigator subscription are restricted by LinkedIn after roughly 300 searches in a calendar month, independently of the Edges quota above. Sales Navigator accounts are not subject to it.
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.
When only_extract_unique_profile is enabled, the action expects exactly one matching person. If the search returns more than one result, the API returns a 404 Not Found with an error message indicating that multiple profiles were found.

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

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: 10 <= x <= 10

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
job_title
string
company_name
string
headline
string
location
string
linkedin_profile_url
string<uri>
profile_image_url
string
linkedin_profile_id
integer
sales_navigator_profile_id
string
connection_degree
string
current_title
string
linkedin_profile_handle
string
shared_connection_search_url
string<uri>
number_shared_connections
integer
shared_connection_profile_urls
string<uri>[]
linkedin_people_post_search_url
string<uri>