Search database companies
Search cached companies. Database mode returns results in under 1 second. Billed per result returned.
Use Case:
Search cached company data with database filters.Pricing
This is a billable endpoint — you are charged for each result returned. If no results are found, the request is free.Authorizations
Use the required Token prefix. Example: Authorization: Token xxxxxxxxx
Body
Industries of the target companies; a company is included if it matches at least one. Values follow LinkedIn's industry taxonomy. Examples: "Software Development", "Financial Services", "Information Technology".
Industries to exclude.
Controls how the industries filter maps onto LinkedIn's industry taxonomy. By default (false), a selected industry also matches companies in its sub-industries. Set to true to match only the industries you specify and exclude their sub-industries, for finer sub-category targeting — for example, "Manufacturing" without "Chemicals".
Company size, as employee-count ranges; a company is included if it falls into at least one. Allowed values: "1-10", "11-50", "51-200", "201-500", "501-1000", "1001-5000", "5001-10000", "10 000+".
Company headquarters locations — matches across cities, states/regions and countries; a company is included if its HQ matches at least one. Examples: "United States", "San Francisco, California, United States", "Germany".
Locations to exclude.
Company types: "Public Company", "Privately Held", "Non Profit", "Government Agency", "Educational", etc.
Exclude companies by LinkedIn ID or URN.
Exclude companies by domain.
Maximum number of companies to return (1-1600).
Number of companies to skip (0-1599, for pagination).
Fields to apply strict matching on (e.g. "company_locations").
Apply Generect's blocked-domain list, which removes staffing agencies, directories and similar low-signal records that match broad industry filters. Set to false to receive them. On by default on the company search endpoints, in both database and realtime mode; the company-leads endpoints do not apply it. In database search the exclusion happens before results_count, so the count always matches what the pages can deliver; in realtime the records are dropped after retrieval, so a page may hold fewer companies than results_count implies.