Skip to main content
Talk to salesStart

LinkedIn filter catalog

Discover supported LinkedIn and Sales Navigator search filters, value shapes, and resolver types.

GET/api/capabilities/linkedin/filters
Scope none (public endpoint)Updated May 11, 2026

This page documents the canonical HTTP contract. Switch to the CLI example when you want the operator workflow.

This endpoint is public and does not require an API key or user session. Its first-party catalog lists normalized field names, provider field names, modes, categories, value shapes, sample values, and resolver types. Catalog contents are the documented set at request time; they do not guarantee a given provider account supports or will accept every listed filter.

CLI

autotouch linkedin filters --api sales_navigator --category people
autotouch linkedin filters --api sales_navigator --category people --field company_size
autotouch linkedin search-params --linkedin-api sales_navigator --type SALES_INDUSTRY --keywords "Software"

Common Sales Navigator fields

  • company_headcount for people search by current company size.
  • headcount, headcount_growth, department_headcount, and technologies for company search.
  • industry, location, current_company, current_title, function, seniority, and persona for people search.

Use this catalog rather than guessing provider parameter names. For ID-backed values, call the Search parameters endpoint with the catalog's resolver_type. The endpoint filters catalog output; it does not validate the parameters of a later provider search.

Query parameters

  • api · optional

    string

    Filter catalog entries by mode: `classic`, `sales_navigator`, or `all`. Omitted also includes all. Unrecognized values produce no matching entries.

  • category · optional

    string

    Filter catalog entries by category: `people`, `companies`, `jobs`, `posts`, or `all`. Omitted also includes all. Unrecognized values produce no matching entries.

  • field · optional

    string

    Optional normalized field name or alias. Available fields and aliases are data-dependent on the current catalog; unknown values may return no matching filter.

Docs