Skip to main content
These routes are not under /v1 yet and will keep working when /v1 replacements are introduced.

Core Concepts

The Workflows API models pipelines as directed acyclic graphs (DAGs):

Execution Flow

  1. List workflows to find the workflow_id you want to run.
  2. Run the workflow with input data and receive a job_id.
  3. Poll live status every 10 seconds or slower until overall_status is no longer queued, running, or finalizing.
  4. Download the result files (CSV, plus JSON or NDJSON when requested).
For workflows that start with a webhook block, see Incoming Webhooks. For recurring runs, see Workflow Schedules.

Quick start

To build workflows without code, use the Workflow Builder in the Sixtyfour web app.

Uploading an input file

Workflows that start with a read_csv block read their rows from a file you upload first.
Enriching a list of people or companies? Use Bulk Intelligence: one call with file and config, no workflow or handle needed.
Send the file as multipart/form-data with a single file part. Accepts .csv, .json, .jsonl, and .ndjson files up to 45 MB. Column names cannot start with _, except _row_id.
cURL
The response returns a handle_id, valid only for your organization:
Pass handle_id as specs_override.resource_handle_id when you call /workflows/run. Runs of a read_csv workflow require it:
cURL

NDJSON input & output

Upload NDJSON or JSONL input the same way as CSV (see Uploading an input file). For NDJSON output, add result_formats=ndjson when running. CSV is always saved; NDJSON is added alongside it. NDJSON keeps numbers, booleans, and nested objects typed, where CSV writes every value as text (lists and objects as JSON).
cURL