Skip to main content
GET
Preview putting a search behind a table

Authorizations

X-API-Key
string
header
required

Path Parameters

table_id
string<uuid>
required

Query Parameters

record_type
enum<string>
required

Which dataset the search would target.

Available options:
people,
companies,
signal_companies,
signal_people,
lookalikes,
local_businesses,
hiring_companies,
backlinks,
search_results,
post_authors,
startup_launches
rows
integer
required

How many rows it would add.

Required range: 0 <= x <= 100000

Response

Successful Response

What putting a search behind a table sets off in the table's own columns, before it runs.

estimated_credits
number
required

The most the table's own columns can cost on the new rows: the columns that run automatically on new rows and read the column the rows land in. Beside the rows' own price and the enrichments the request ticks, which are priced as for a new table. Zero when none of the table's columns would run.

expected_credits
number
required

What those columns usually cost on the new rows; never above estimated_credits. Quote both, this first.

The table already has a search. A table carries one, so putting another behind it is refused (409); add rows from its own search with more_rows on its run instead.