/v1/actions/salesnavigator-search-metrics/run/liveSearch Sales Navigator Metrics returns a ready-to-query metrics search URL for a company on Sales Navigator, starting from a company ID. You get the canonical URL that surfaces workforce statistics — headcount trends, hiring velocity, function and geography breakdowns — so you can route it into analytics, insights pipelines, or follow-up extractions.
This action runs on the Sales Navigator level and is aimed at analysts, RevOps teams, and signal-driven sellers who want structured access to the metrics layer rather than screenshots.
You pass a Sales Navigator company ID, Edges builds the Sales Navigator metrics search URL that matches that account, and returns it through your authenticated session. The URL is the anchor for every downstream metrics call — you can fetch it directly or chain it into the other metrics-extraction actions in the library.
Everything runs on Edges infrastructure: authenticated through the Sales Navigator account you connected, rate-limited safely, and browser-less. The operation is live, so the URL comes back in a single round trip.
Use Search Sales Navigator Metrics when you want the metrics view as a first-class primitive — a URL you can store, share, or pass to downstream scrapers. It plugs into the LinkedIn signals & intent API use case where hiring growth, sudden attrition, or function-specific expansion are your trigger events.
It pairs well with headcount extraction actions to turn a URL into rows of signal data.
One per run, since the action is scoped to a single company ID. For bulk runs, iterate your account list and fire the action per row.
Your own Sales Navigator session. Edges signs every request with your connected account, so the URL reflects the filters and access your seat has.
Yes. Most teams chain it after an account resolver and before a metrics extractor — for example, Extract Sales Navigator Company Employee Count to get the actual headcount number.
Run Search Sales Navigator Metrics from the Edges library, wire it into a signals pipeline, or call it directly from the Edges API. Browse the full Actions library to see what to chain on top of the metrics URL.
curl -X POST "https://api.edges.run/v1/actions/salesnavigator-search-metrics/run/live" \
-H "X-API-KEY: <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{
"identity_ids": [
"your-identity-uuid"
],
"identity_mode": "direct",
"input": {
"custom_data": "example_value",
"sales_navigator_company_id": "example_value",
"sales_navigator_profile_search_url": "https://www.linkedin.com/in/example-profile"
},
"parameters": {
"geo": "example_value",
"geography_excluded": [
"item1",
"item2"
],
"function": "example_value",
"function_excluded": [
"item1",
"item2"
],
"seniority": [
"item1",
"item2"
],
"seniority_level_excluded": [
"item1",
"item2"
],
"employees_title": "example_value",
"current_job_title_excluded": [
"item1",
"item2"
],
"exclude_saved_leads": true,
"exclude_crm_contacts": true,
"exclude_viewed_leads": true,
"keywords": "example_value"
}
}'{
"sales_navigator_company_url": "https://www.linkedin.com/in/example-profile",
"company_name": "Example Name",
"sales_navigator_company_id": 42,
"linkedin_company_url": "https://www.linkedin.com/in/example-profile",
"total_leads": 42,
"new_leads": "example_value",
"leads_posted_recently": "example_value",
"leads_mentioned_in_news": "example_value",
"leads_with_common_experience": "example_value",
"leads_following_your_company": "example_value",
"leads_past_colleague": "example_value",
"leads_teamlink_your_executives": "example_value",
"leads_viewed_profile_recently": "example_value"
}