Skip to main content
POST
Search Company Launcher
Search Company OverviewYou input: Industry, headquarters country, or headcount range (at least one required)You get: Company profiles with domain, LinkedIn, employee count, industry, HQ location, and funding details
Search Company returns results synchronously — output.companies is included directly in the response. There is no separate polling step.

Filters

At least one of the following must be provided: All three can be combined — results must match all provided filters.

Output

Each company in output.companies includes name, domain, LinkedIn, employee count, industry, founding year, address, and funding details where available.

Authorizations

x-api-key
string
header
required

To access the API, provide your API key in x-api-key.

Body

application/json

Search Company request payload with company filters, pagination, and optional custom_fields.

Request payload for Search Company. At least one non-empty list among industries, location_countries, or sizes must be provided.

industries
string[]
required

Industry filters used to match companies.

Required array length: 1 - 50 elements

LinkedIn industry filter value. Use title-case industry names from the supported industry list: https://waterfall-io-public.s3.us-east-1.amazonaws.com/industries.txt.

Required string length: 5 - 57
Example:
location_countries
string[]

Country filters used to match companies.

Maximum array length: 50

Country filter value for Search Company.

Required string length: 4 - 40
Example:
sizes
enum<string>[]

LinkedIn employee-size buckets used to filter companies.

Maximum array length: 8

LinkedIn employee-size bucket.

Available options:
1-10,
11-50,
51-200,
201-500,
501-1000,
1001-5000,
5001-10000,
10001+
Example:
page_number
integer<int32>
default:1

Page number for paginated Search Company results.

Required range: 1 <= x <= 100
Example:

1

page_size
integer<int32>
default:20

Number of companies to return per page in Search Company.

Required range: 1 <= x <= 250
Example:

20

custom_fields
object | null

Optional custom key-value metadata echoed on job input and output (useful for correlating internal source metadata). On create requests, omit the field or send JSON null when no custom fields are needed; both are stored as {}. When present, the value must be a JSON object with keys matching ^[A-Za-z0-9_-]+$ and values that are a string (max 1000 characters), number, or boolean. Empty string, arrays, and other non-object types return HTTP 400. On job GET responses, input.task.custom_fields is always an object ({} or populated).

Example:

Response

Search Company result returned successfully.

Search Company response with job state, input, and optional output.

status
enum<string>
required

The status of the job.

Available options:
RUNNING,
SUCCEEDED,
FAILED,
TIMED_OUT,
ABORTED
Example:

"RUNNING"

start_date
string<date-time>
required

A date time in ISO 8601 format.

Example:

"2025-02-05T15:46:35.771751+00:00"

input
object
required
Example:
stop_date
string<date-time>

A date time in ISO 8601 format.

Example:

"2025-02-05T15:46:35.771751+00:00"

output
object

Search Company output payload.

Example: