Replace
YOUR_API_KEY in each example with your actual API key. All
requests require the x-api-version: 2025-11-01 header.Request body
| Parameter | Type | Required | Description |
|---|---|---|---|
filters | array | Yes* | Array of Sales Navigator filter objects. Each has field, type, and value. |
professional_network_search_url | string | Yes* | A LinkedIn Sales Navigator search URL. |
page | integer | Yes (with filters) | Page number (1–65). Each page returns up to 25 results. |
filters or professional_network_search_url, not both.
Response body
| Field | Type | Description |
|---|---|---|
companies | array | Company profiles matching the search. |
total_display_count | string | Total matching companies (e.g., "32K+"). |
Rate limits and credits
Current platform behavior — not specified in the OpenAPI contract:
- Rate limit: 60 requests per minute.
- Credits: 1 credit per company returned.
- Page limit: Up to ~65 pages (up to ~1,625 results). Split broad queries into smaller filter sets if you need more.
Two ways to search
You can search using either:- A Sales Navigator search URL — paste a URL directly from your browser.
- Structured filters — define filter criteria in your request body.
Search vs Realtime Search
| Search | Realtime Search | |
|---|---|---|
| Data source | Crustdata indexed database | LinkedIn Sales Navigator (live) |
| Filter syntax | { "field": "dotpath", "type": "op", "value": ... } | [{ "field": "ENUM_TYPE", "type": "in", "value": [...] }] |
| Filter field names | Dot-path fields like locations.hq_country | LinkedIn enums like REGION, INDUSTRY |
| Country values | ISO3 codes ("USA", "GBR") | Full names ("United States") |
| Operators | =, !=, >, <, =>, =<, in, not_in, is_null, is_not_null, (.), [.] | in, not_in |
| Boolean logic | Nested and/or groups | Multiple filters combined with implicit AND |
| Pagination | Cursor-based (cursor + next_cursor) | Page-based (page 1–65, 25 results per page) |
| Response shape | { companies, next_cursor, total_count, query } | { companies, total_display_count } |
| Field selection | fields parameter to choose response fields | Not supported — returns all available fields |
| Best for | Structured segmentation, large-scale list building, precise filters | Live prospecting, hiring signals, funding events |
Search by Sales Navigator URL
If you already have a LinkedIn Sales Navigator search URL, pass it directly.Response
Search by structured filters
Use thefilters array to define search criteria programmatically. Each filter has a field, type (operator), and value.
Find mid-size tech companies
This search finds companies with 51–200 employees in the Technology industry.Response trimmed to one company for clarity. The API returns up to 25 companies per page.
The OpenAPI spec defines
year_founded as a nullable string (e.g., "1998"). However, actual API responses may return this field as an integer (e.g., 1998). Handle both types in your integration.Understanding the response
Every realtime search response has two fields:companies— an array of company profiles matching your search. Each profile includes basic info, headcount, taxonomy, location, revenue estimates, and decision-maker counts.total_display_count— the total number of matching companies across all pages (as a string, e.g.,"32K+"). This is approximate — LinkedIn does not provide exact counts for large result sets.
How to interpret results
total_display_countis a string: Values like"32K+"mean approximately 32,000+ matches. Parse as an approximate indicator, not an exact count.- Empty
companiesarray: No more results for this page. Stop paginating. - Field names differ from indexed Search: Realtime results use
professional_network_url(notprofile_url) andprofessional_network_id(notlinkedin_id).
More filter examples
Large companies outside the US with revenue 500M
Companies hiring on LinkedIn
Recently funded companies
Paginate through results
Use thepage parameter to walk through pages of results. Each page returns up to 25 companies.
First page: set page to 1.
Next page: increment page by 1 and repeat the same request.
page until the companies array comes back empty.
Filter object schema
Each filter in thefilters array must have this shape:
| Key | Type | Required | Description |
|---|---|---|---|
field | string | Yes | A Sales Navigator filter type (see table below). |
type | string | Yes | Operator: "in" or "not_in". |
value | string or string[] | Yes | A string or array of strings matching the filter field’s expected values. |
All filters in the array are combined with implicit AND logic. Nested
or groups are not supported in Realtime Search — use indexed Search for complex boolean queries.Available filter fields
| Field | Description | Operators | Example values |
|---|---|---|---|
INDUSTRY | LinkedIn industry | in, not_in | "Software Development" |
COMPANY_HEADCOUNT | Employee count range | in, not_in | "51-200", "1,001-5,000" |
REGION | Geographic region | in, not_in | "United States", "Europe" |
COMPANY_HEADQUARTERS | HQ location | in, not_in | City or country names |
ANNUAL_REVENUE | Revenue range | in, not_in | "1-500" (string values per the spec) |
NUM_OF_FOLLOWERS | LinkedIn follower count | in, not_in | Follower count ranges |
FORTUNE | Fortune list | in | "Fortune 500" |
DEPARTMENT_HEADCOUNT | Department size | in, not_in | Department headcount ranges |
DEPARTMENT_HEADCOUNT_GROWTH | Dept growth rate | in, not_in | Growth rate ranges |
COMPANY_HEADCOUNT_GROWTH | Headcount growth | in, not_in | Growth rate ranges |
KEYWORD_COMPANY | Keyword search | in | Any keyword string |
ACCOUNT_ACTIVITIES | Company activities | in | "Funding events in past 12 months" |
JOB_OPPORTUNITIES | Hiring activity | in | "Hiring on Linkedin" |
Filter values use LinkedIn’s vocabulary, not Crustdata’s indexed values. For example, regions use full names like
"United States", not ISO3 codes like "USA". There is no autocomplete endpoint for Realtime Search values — refer to LinkedIn Sales Navigator for valid options.Supported operators
| Operator | Description | Use with |
|---|---|---|
in | Value is in list | Most filter fields |
not_in | Value is not in list | REGION, INDUSTRY, etc. |
Response fields
Each company in the response includes these sections:| Section | Key fields | Description |
|---|---|---|
basic_info | name, professional_network_url, primary_domain, description, year_founded, industries | Core identity and profile |
headcount | total | Total employee count |
taxonomy | linkedin_industry | LinkedIn industry classification |
locations | hq_country, hq_city, hq_state, headquarters | Headquarters location |
revenue | estimated.lower_bound_usd, estimated.upper_bound_usd | Revenue range estimate |
people | decision_makers_count | Number of decision makers |
Validation rules
| Rule | Behavior |
|---|---|
filters or professional_network_search_url | Provide one or the other, not both. Sending both returns an error. |
page with filters | Required when using filters. Range: 1–65. |
page with URL | Not required. URL-mode returns the first page of results. |
| Empty results | Returns 200 with an empty companies array. |
Errors
400 — Invalid filter key
401 — Invalid API key
API reference summary
| Detail | Value |
|---|---|
| Endpoint | POST /company/professional_network/search/live |
| Auth | Bearer token + x-api-version: 2025-11-01 |
| Request | filters array OR professional_network_search_url (mutually exclusive), plus page (1–65) |
| Response | { companies, total_display_count } |
| Pagination | Page-based. 25 results per page. Increment page until companies is empty. |
| Empty result | 200 with "companies": [] |
| Errors | 400 (bad filter/URL), 401 (bad auth), 500 (server error) |
Filter vocabulary comes from LinkedIn Sales Navigator. There is no autocomplete endpoint for Realtime Search values.
What to do next
- Search Crustdata’s database — use Company Search to query indexed company data with more filter options and sorting.
- Enrich a company — use Company Enrich to get a detailed profile for a known company.
- See more examples — browse company examples for ready-to-copy patterns.
- Full API reference — see the OpenAPI spec for the complete request/response schema.

