Skip to Content
API & MCPPOSTExport a full company list

Exports & jobs

Export a full company list

Export EVERY company matching a search or a lookalike — not just the top 100.

POST/v1/exports
MCP tool start_exportscope exports:create1 record per exported row (company or person)

Parameters

searchobjectoptional
similarobjectoptional
peopleobjectoptional
min_similaritynumberoptional
(min 0, max 1)
max_rowsintegeroptional
(min 1, max 1000000)
format"csv" | "jsonl"optional
namestringoptional
idempotency_keystringoptional

What your agent reads

The tool description exactly as an MCP client receives it in tools/list — it doubles as the full behaviour of the endpoint.

Export EVERY company matching a search (`search`: the same arguments as search_companies) or a lookalike (`similar`: the same arguments as find_similar) — not just the top 100. Or EVERY PERSON of a people search (`people`: the arguments of search_people, list or waterfall — no 10,000 depth limit, no company cap: a large company scope is run part by part). People files carry contacts; records: one per row (company or person) in the file. Exact scan: nothing above `min_similarity` (cosine, default 0.5) is missed. A `search` with only filters (no match/concept/sells_to) exports EVERY company that passes them, ordered by industry confidence (score empty; min_similarity does not apply). Runs in the background: returns a job_id; poll get_job until status='done', then give the user the download link (CSV or JSONL, valid 24 h, re-issued by get_job). Each exported row costs records (see get_usage); the export is capped at what is left in your 5-hour and weekly windows and your plan's export size, so it never overdraws. Size it first with count_companies. Pass an idempotency_key when retrying so a retry never starts a second export. EXCLUSION: exclusion lists marked auto_exclude apply automatically — organization-wide ones to every call, a CLIENT's ones (agencies) only to calls made for that client (`client`, or an API key bound to it); add more per call with `exclude_lists` (ids from get_lists) or `exclude_domains` (up to 1000 domains, URLs or e-mail addresses). An excluded company never appears — not in results, counts, lookalikes or exports. `applied_exclusions` in the response lists what was applied. QUALITY: gambling and adult sites and non-organisations (parked or for-sale domains, empty sites, personal pages) are left out by default. Name the vertical or leaf facet yourself to override (e.g. filters={vertical:'gambling_betting'}).

Errors follow one format.