Skip to main content
POST
Search People Nav

Overview

Run a Sales Nav lead search and get back richly-detailed leads. This uses the account’s Sales Nav seat — see Connect Account to activate it. There are two ways to define the search — pick whichever fits:
  1. Friendly filters — pass human-readable values (e.g. seniority_level: ["Director", "CXO"]) and the API resolves them to the underlying ids for you.
  2. Copied Sales Nav URL — build the search visually in Sales Nav, copy the page URL, and pass it as sales_nav_url. Every filter is replicated verbatim, including ones with no friendly mapping (buyer intent, spotlights, …). Saved-search and lead-list URLs work too.
This endpoint consumes 1 credit per 10 results returned. Requires a Sales Nav seat on the account. Ignore this if you’re on per-seat pricing: usage is unlimited.
Within a single filter, multiple values are combined with OR (e.g. seniority_level: ["VP", "CXO"] = VP or CXO). Different filters are combined with AND.

Request

string
required
Your API key for authentication.
string
required
The unique identifier of the account to use. Must have a Sales Nav seat.
string
required
Must be "search_people_nav".
object

Paging

offset: 0, count: 25 returns leads 0–24, offset: 25 the next 25. The response echoes offset back, so the next page is offset + total_results.
Sales Nav only lets a single search be browsed up to 2500 results, whatever total_available_results reports. An offset of 2500 or more returns INVALID_PARAMS (0 credits) — narrow the filters to reach deeper leads.
Every list filter also accepts raw ids directly, so you can mix friendly names and ids. Unknown values are ignored rather than causing an error.

Response

boolean
Indicates whether the request was successful.
object

Examples

Friendly filters

Exclusions

Copied Sales Nav URL

Lists and lead profile

Same seat, same endpoint, 1 credit per call:
  • list_lists_nav { type?: "lead"|"account", ownership?: "all"|"owned"|"editable", offset?, count? }: the seat’s lists, each with list_id, name, type and entity_count.
  • create_list_nav { name, type: "lead"|"account", description? }: creates an empty list and returns its list_id.
  • add_to_list_nav { list_id, profiles? | companies? }: adds up to 25 profiles (URLs or ids) to a lead list, or up to 100 companies (ids or URLs) to an account list. Each input gets a status: added, already_in_list, or failed with an error. Costs 1 credit per 10 entities.
  • remove_from_lists_nav { profiles? | companies? }: unsaves leads or companies. LinkedIn has no per-list removal, so they leave every list of the seat. Same limits, status (removed or failed) and pricing as add_to_list_nav.
  • delete_list_nav { list_id, unsave_entities?: false }: deletes a list. Its leads stay saved in their other lists unless unsave_entities is true.
  • get_profile_nav { profile }: a lead as Sales Nav shows it, with positions, education, the emails visible to the seat, inmail_restriction, open_link, saved and list_count.
To read a list, pass it to this search as lead_list or as a .../sales/lists/people/<id> URL. list_saved_searches_nav { type?: "people"|"company", offset?, count? } returns the seat’s saved searches with saved_search_id, name, last_viewed_at (epoch ms, like the lists’ created_at) and new_results_count. Run a saved people search again with saved_search_id on this search. save_search_nav { name, type?: "people"|"company", ...filters } saves a search built from the same filters as this search or Search Companies Nav (or their sales_nav_url) and returns its saved_search_id; a name already used on the seat is refused. delete_saved_search_nav { saved_search_id } deletes one.