curl --request POST \
--url https://api.sixtyfour.ai/bulk-intelligence/company \
--header 'Content-Type: multipart/form-data' \
--form 'file=<string>' \
--form 'config=<string>'{
"task_id": "<string>",
"status": "<string>",
"row_count": 123,
"estimated_cost_cents": 123,
"already_started": true
}Start Company Bulk Intelligence
Upload a CSV/JSON/NDJSON tabular file and start an inline bulk intelligence run.
Bulk runs execute in the background. Poll GET /job-status/{task_id};
when the job completes the response includes signed download links for
result files and charge_amount (total cents actually charged).
/workflows/runs/{task_id}/live_status remains available for per-block
progress. Row-level enrichment failures pass through un-enriched rows;
source-block failures fail the run. Without a webhook, use enrichment block
artifacts. With a webhook, webhook block artifacts may add webhook result
columns while the enrichment artifacts remain available from the prior block.
curl --request POST \
--url https://api.sixtyfour.ai/bulk-intelligence/company \
--header 'Content-Type: multipart/form-data' \
--form 'file=<string>' \
--form 'config=<string>'{
"task_id": "<string>",
"status": "<string>",
"row_count": 123,
"estimated_cost_cents": 123,
"already_started": true
}Headers
Optional idempotency key for retry-safe bulk submissions.
Body
Response
Successful Response
Response when a bulk intelligence job is started.
Job ID. Poll GET /job-status/{task_id}; on completion the response includes signed download links for result files.
Job status, typically 'RUNNING'.
Number of parsed input rows; omitted on idempotent replays.
Estimated job cost in cents (rows × per-row tier price). A floor: options like find_people can bill more. Omitted on idempotent replays.
True when the request was deduplicated via Idempotency-Key header.
Was this page helpful?