Long-running work

Plenty of calls in this API start work rather than finish it. They answer 202 Accepted with a handle, and the work lands over the following seconds or minutes. There is no single poller. The handle you get back tells you which one to use, and they are not interchangeable — this page maps them.

What 202 means

A 202 means the request was accepted and validated, not that the work succeeded. Two things follow from that:

Credits are usually spent by the background work, not the call. A 202 is not a receipt.
Failure arrives later. A job can accept cleanly and then fail per row, or find nothing at all.

Most calls that answer 200 or 201 have already finished by the time you read it. One exception: POST /business/campaigns answers 201 with status: "initializing", and an AI-generated campaign keeps preparing its steps in the background.

Which handle to poll

What you started	You get back	Follow it with
Export a list	`jobId`	`GET /business/exports/{jobId}`
A CRM-side job (`jobId` is 24-hex)	`jobId`	`GET /business/jobs/{jobId}`
Create an AI-generated campaign	`campaignId`, `status`	`GET /business/campaigns/{campaignId}` until `initializationStatus` is `completed`
Approve a campaign	`campaignId`, `status`	`GET /business/campaigns/{campaignId}`
Smart column create or re-run	`jobId`	`GET /business/lists/{listId}/smart-columns/{jobId}/status`
Import commit	`import.listId` and `import.jobId` (a UUID)	the destination list’s `completionStatus` — see below
Enrich a list (`email`, `phone`, `phone_and_email`)	`jobId` and `status`	`GET /business/jobs/{jobId}`, see below
Enrich a list (`validate_emails`, `demographics`)	`listIds`	the list’s `completionStatus`
Save a search to a list with `enrich: "none"`	`listIds`	the list’s `completionStatus`
Save a search to a list with `enrich` set	`listIds`, `jobId` and `status`	`GET /business/jobs/{jobId}`. The list reads `complete` until the job starts, so do not wait on it.
Save a company search, copy rows between lists, derive a company list	`listIds`, or `list.id`	the list’s `completionStatus`
Scan or merge duplicates	`jobId`	`GET /business/contacts/dedupe-jobs/{jobId}`
Push a list to your CRM	`crm`, `listIds`	Nothing to poll; records appear in the CRM as the sync runs
Start an agent	the agent	`GET /business/agents/{agentId}` and read `status`
Start a research run	`run.runId`	`GET /business/research/runs/{runId}/events`, or `GET /business/research/runs/{runId}`
Build a knowledge hub	the hub	`GET /business/knowledge-hubs/{hubId}` and read `status`
Count people or companies on the Data API	`status: "pending"` and the `filters` being counted	The same request again with those `filters`, until it answers `200` with `status: "ready"`
Enrich up to 100 people on the Data API	`jobId` and `status`	`GET /business/data/people/enrich-jobs/{jobId}`

GET /business/jobs/{jobId} serves CRM async jobs and enrichment jobs — the 24-character hex ids. An import commit returns a UUID, which that endpoint refuses with 422. Follow an import through its destination list instead. A Data API job’s jobId is 24-hex too, but only GET /business/data/people/enrich-jobs/{jobId} serves it.

Following a list that is filling

Saving a search without enrichment, committing an import, copying rows and deriving a company list all work the same way: the list exists immediately and fills in the background. Read the list and watch completionStatus. When enrichment is involved, follow its job instead, because the list only turns processing once the job starts.

curl https://api.tryfuse.ai/api/v1/business/lists/$LIST_ID -u "$FUSE_API_KEY:"

Row counts climb while it runs, so a list that reports rows is not necessarily finished.

Following a job

The smart-column status poller reports progress and what the run has spent so far:

{
  "job": {
    "status": "processing",
    "totalRows": 100,
    "processedRows": 40,
    "successfulRows": 38,
    "failedRows": 2,
    "creditsUsed": 76
  }
}

failedRows is worth reading on every poll. A job can complete with failures — those rows simply have no answer — and nothing else will tell you.

Following an enrichment job

Enriching a list, or saving a search with enrich set, starts an enrichment job. Its poll at GET /business/jobs/{jobId} has type: "bulk_enrichment" and also carries the lists the run fills and its counts so far:

{
  "job": {
    "jobId": "68a2109c9c41d20014b41002",
    "type": "bulk_enrichment",
    "status": "processing",
    "rowCount": null,
    "downloadUrl": null,
    "error": null,
    "listIds": ["68a1f20b9c41d20014b3e901"],
    "progress": {
      "totalContacts": 200,
      "processedContacts": 80,
      "enrichedContacts": 61,
      "notFoundContacts": 12,
      "alreadyEnrichedContacts": 7,
      "creditsCharged": 7050
    }
  }
}

`status`	Means
`pending`	Waiting for your other enrichment job to finish. Your enrichment jobs run one at a time, whether started through the API or in the app.
`processing`	Running. A job started by saving a search first looks up the company names in its filters that Fuse’s own company records do not answer, before it saves anyone, so a long list of names can keep it here with no progress for several minutes. The list’s `completionStatus` can turn `complete` while the job is still `processing`: its last, slower lookups only add values to rows already on the list.
`stopped`	Paused because the balance ran out, with `pausedReason: "INSUFFICIENT_CREDITS"`. Top up, then resume it from the list’s page in the app. It does not resume on its own.
`completed`	Done.
`cancelled`	Cancelled from the app. What it found before that is kept.
`failed`	Ended by an error, with `error: "ENRICHMENT_FAILED"`. What it found before that is kept. A job started by saving a search also ends this way when its filters no longer give the same search on a later page, which can happen when it resumes after a long pause, and when the company names in its filters still cannot all be looked up after about 25 minutes. In that case it fails before it has saved or charged anything.

Stop polling on completed, cancelled or failed. A stopped job only moves again after a resume in the app, so poll it rarely, if at all.

Following a research run

Research runs report a stream of events rather than a percentage, because the interesting part is what the run is doing:

curl -G https://api.tryfuse.ai/api/v1/business/research/runs/$RUN_ID/events \
  --data-urlencode "sinceSeq=0" \
  -u "$FUSE_API_KEY:"

Each event carries a seq. Pass the last one you saw as sinceSeq on the next call to get only what is new, and stop when the run’s status is terminal.

How often to poll

Every poll counts against your rate limit, and several families share one bucket. A few rules that keep you inside it:

Wait before the first poll

Nothing meaningful has happened one second after a 202.

Back off as it runs

A few seconds apart early, then widen. Long jobs rarely need per-second resolution.

Use the cursor where there is one

sinceSeq on research events returns only new events instead of the whole history.

Stop on a terminal status

Poll a finished job and you are spending rate limit on a fixed answer.

On 429, wait for the window named in the response headers rather than retrying immediately.

Get started

Concepts

Guides

Workflows

CRM sync

Power dialer

Deep Research

Signals

MCP server

Long-running work

What 202 means

Which handle to poll

Following a list that is filling

Following a job

Following an enrichment job

Following a research run

How often to poll

​What 202 means

​Which handle to poll

​Following a list that is filling

​Following a job

​Following an enrichment job

​Following a research run

​How often to poll

What 202 means

Which handle to poll

Following a list that is filling

Following a job

Following an enrichment job

Following a research run

How often to poll