Skip to main content
POST
Create a table from a signal search

Authorizations

X-API-Key
string
header
required

Body

application/json

Run a signal search and land it in a new table.

signal_type
enum<string>
required

Which buying signal a search is looking for.

Each member names one discovery question the provider can answer, and each maps to exactly one upstream endpoint. The last two are firmographic rather than event-shaped — they find companies by what they ARE rather than by what they DID — and are kept in the same enum because they land the same company rows through the same machinery.

Available options:
hiring,
news,
technology,
portfolio_companies,
financing,
products,
firmographics,
extended_firmographics
table_name
string
required
Required string length: 1 - 255
query
SignalQuerySchema · object

Every filter any signal type can take.

ONE schema for all eight types, mirroring the domain's single query dataclass. Which of these a given signal type actually accepts is decided by the domain's per-type allow-list, and a filter the type cannot use is REJECTED with a 422 naming it — never quietly dropped.

An empty query is valid here. Discovery is bounded by the row cap rather than by the filters, so "the companies that most recently raised" is a legitimate search.

row_limit
integer | null

Company rows to land. Clamped by the product's own ceiling and by the plan's rows-per-table limit; null uses the product default.

Required range: x >= 1

Response

Successful Response

The table a signal search was turned into.

rows_created
integer
required
rows_matched
integer
required

Companies the search returned. Larger than rows_created when some of them were already in the table.

table_id
string<uuid>
required
table_name
string
required
technology
ResolvedTechnologySchema · object | null
required

The provider's own entry for the technology that was searched.