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

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

A search plus a new table to put its results in.

enrichments
enum<string>[]
required

What to find out about the rows this lands. At least one is required: a table of names with nothing found out about them is a list, not a workspace. Each becomes its own column, and each is billed per row that comes back with an answer.

Required array length: 1 - 4 elements

An enrichment offered at import, in the user's vocabulary not the catalog's.

Each option names an outcome and resolves to the curated enrichment that delivers it, so importing leads stays a question about what you want rather than about who supplies it.

Kept as its own enum rather than reusing the capability keys directly: the import page offers a deliberately short list, and which enrichments belong on it is a product decision that should not change every time the catalog gains a capability.

Available options:
find_email,
find_phone,
enrich_contact,
enrich_company
record_type
enum<string>
required

Which side of the lead database a search runs against.

Available options:
people,
companies
table_name
string
required
Required string length: 1 - 255
companies
CompanyQuerySchema · object | null

Filters for a company search.

people
PeopleQuerySchema · object | null

Filters for a people search.

row_limit
integer | null

Rows to land. Clamped further by the organisation's plan cap; omit for the maximum.

Required range: 1 <= x <= 250000

Response

Successful Response

The table a search produced.

rows_created
integer
required
table_id
string<uuid>
required
table_name
string
required
total_matched
integer
required
enrichments_applied
enum<string>[]

Chosen enrichments that became a column on the new table.

An enrichment offered at import, in the user's vocabulary not the catalog's.

Each option names an outcome and resolves to the curated enrichment that delivers it, so importing leads stays a question about what you want rather than about who supplies it.

Kept as its own enum rather than reusing the capability keys directly: the import page offers a deliberately short list, and which enrichments belong on it is a product decision that should not change every time the catalog gains a capability.

Available options:
find_email,
find_phone,
enrich_contact,
enrich_company
enrichments_skipped
enum<string>[]

Chosen enrichments no provider could run against the records this search returned — leads with no LinkedIn URL cannot be enriched from one. The table is still created.

An enrichment offered at import, in the user's vocabulary not the catalog's.

Each option names an outcome and resolves to the curated enrichment that delivers it, so importing leads stays a question about what you want rather than about who supplies it.

Kept as its own enum rather than reusing the capability keys directly: the import page offers a deliberately short list, and which enrichments belong on it is a product decision that should not change every time the catalog gains a capability.

Available options:
find_email,
find_phone,
enrich_contact,
enrich_company