> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sixtyfour.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Legacy Outgoing Webhooks

> Receive HTTP notifications from Sixtyfour when async jobs and workflows complete.

This page documents webhooks for the original routes, which keep working. For new integrations, see [Outgoing Webhooks](https://docs.sixtyfour.ai/api-reference/webhooks/outgoing.md).

Outgoing webhooks come from two sources:

| Source | Trigger | Payload |
| - | - | - |
| Async-job webhook | `webhook_url` in the body of an async endpoint | Job result response |
| Workflow `outgoing_webhook` block | The block in a workflow | Workflow run response with results |

Headers, signing, retries and destination checks are the same for both sources. The payload and the accepted URL schemes differ.

## Async-job webhooks

Pass an optional `webhook_url` in the request body. When the job completes, Sixtyfour POSTs the result to that URL. Synchronous `/people-intelligence` and `/company-intelligence` requests that include `webhook_url` also send this callback.

### Supported endpoints

| Endpoint | Callback |
| - | - |
| `/find-email-async`, `/find-email-bulk-async` | Job result response |
| `/find-phone-async`, `/find-phone-bulk-async` | Job result response |
| `/reverse-email-async`, `/reverse-email-bulk-async` | Job result response |
| `/reverse-phone-async`, `/reverse-phone-bulk-async` | Job result response |
| `/people-intelligence-async` | Job result response |
| `/company-intelligence-async` | Job result response |
| `/bulk-intelligence/people`, `/bulk-intelligence/company` | [Workflow run response](#workflow-webhooks), with `run_id` set to the job's `task_id`. Set `webhook_url` in the job config; the result file gains `webhook_status_code`, `webhook_response` and `webhook_success` columns. See [Bulk Intelligence](https://docs.sixtyfour.ai/api-reference/legacy/bulk-intelligence.md#webhook-callback). |
| `POST /monitors`, `POST /monitors/linkedin`, `POST /monitors/upload` (`config.webhook_url`), `POST /monitors/{monitor_id}/update`, and the workflow [`monitor` block](https://docs.sixtyfour.ai/api-reference/workflows/workflow-blocks#monitor) | Monitor notifications. See [Monitor Notifications](https://docs.sixtyfour.ai/api-reference/monitors/monitor-notifications.md). |

Async-job endpoints and Bulk Intelligence accept only `https://` URLs. Monitors and the workflow `outgoing_webhook` block accept `http://` and `https://`. Every destination must pass the [URL rules](#url-rules). For rejected URLs, see [Handling Errors](https://docs.sixtyfour.ai/api-reference/legacy/errors.md).

### Request

`POST /find-email-async`:

```json theme={null}
{
  "lead": {
    "name": "Saarth Shah",
    "company": "Sixtyfour",
    "linkedin_url": "https://www.linkedin.com/in/saarthshah"
  },
  "webhook_url": "https://your-server.com/webhooks/sixtyfour"
}
```

The endpoint returns a `task_id` immediately:

```json theme={null}
{
  "task_id": "550e8400-e29b-41d4-a716-446655440000",
  "status": "RUNNING",
  "total_leads": 1,
  "mode": "PROFESSIONAL"
}
```

### Payload

```json theme={null}
{
  "task_id": "550e8400-e29b-41d4-a716-446655440000",
  "status": "completed",
  "task_type": "find_email",
  "result": {
    "leads": [
      {
        "name": "Saarth Shah",
        "company": "Sixtyfour",
        "email": [["saarth.work@example.com", "OK", "COMPANY"]],
        "other_emails": []
      }
    ],
    "total_leads": 1,
    "emails_found": 1,
    "cost_cents": 5,
    "cost_credits": 0.5,
    "mode": "PROFESSIONAL"
  },
  "error": null,
  "event_id": "f7c2a4e0-9b5d-4a1f-8d2c-1e3b5f7a9c0d",
  "attempt": 1
}
```

| Field | Type | Description |
| - | - | - |
| `task_id` | string | The job's ID, as returned by the async endpoint. |
| `status` | string | `completed`. |
| `task_type` | string \| null | Job type. See the table below. |
| `result` | object | The job result. See [Result fields by endpoint](#result-fields-by-endpoint). |
| `error` | null | Always null. Failures are reported through `/job-status/{task_id}`. |
| `event_id` | string (UUID) | Unique per delivery and the same across its retries. A job can send more than one delivery, each with its own `event_id`, so dedupe on `task_id`. |
| `attempt` | integer | Delivery attempt, starting at `1`. |
| `investigation` | object | People Intelligence `xhigh` only: `{ "id", "workspace_url" }` of the [Atlas investigation](https://docs.sixtyfour.ai/atlas/integrations.md#webhooks) the job created. |

### Result fields by endpoint

| Endpoint family | `task_type` | `result` shape |
| - | - | - |
| Find Email | `find_email` | `leads`, `total_leads`, `emails_found`, `cost_cents`, `cost_credits`, `mode` |
| Find Phone | `find_phone` | `leads`, `total_leads`, `phones_found`, `cost_cents`, `cost_credits` |
| Reverse Email, Reverse Phone | `reverse_enrichment` | `leads`, `total_leads`, `successful_lookups`, `cost_cents`, `cost_credits` |
| People Intelligence | `lead_enrichment` | Same as the job-status `result`. `xhigh` jobs also carry the research notes, graph and workspace files. |
| Company Intelligence | `company_enrichment` | Same as the job-status `result` |

Contact lookups wrap records in `result.leads`, even for one record; `GET /job-status/{task_id}` returns a single record as `result` ([details](https://docs.sixtyfour.ai/api-reference/legacy.md#contact-lookups-in-job-status-and-webhooks)). `cost_credits` is the amount charged; `cost_cents` is deprecated. A non-null `task_type` matches the `Sixtyfour-Event-Type` header and job status.

For People Intelligence and Company Intelligence, the callback can arrive before `GET /job-status/{task_id}` reads `completed`. Read `charge_credits` once it does. See [Async jobs](https://docs.sixtyfour.ai/api-reference/async-jobs.md#webhooks).

### Job failures

Sixtyfour sends callbacks for completed jobs only; failed, cancelled and timed-out jobs send none. If no callback arrives by your deadline, poll `GET /job-status/{task_id}`.

## Workflow Webhooks

Add an `outgoing_webhook` block to POST the run's results to your URL. The block sends one request per run, not per row. When no rows reach the block, for example because a filter removed every row, it sends nothing. To catch that case, poll the run's [live status](https://docs.sixtyfour.ai/api-reference/legacy/workflows-execution.md#get-live-status) when no delivery arrives.

### Block specs

| Field | Type | Default | Description |
| - | - | - | - |
| `url` | string | required | Destination URL. `http://` or `https://`, public host only. |
| `headers` | object | none | Extra request headers. Invalid header names are dropped. |
| `timeout_seconds` | float | `10` | Per-attempt timeout in seconds, up to 150. Values up to 300 are accepted and run as 150. |
| `include_csv_download_link` | boolean | `false` | Include download URLs for the previous block's results. The delivery waits up to 120 seconds for them; a URL that isn't ready by then is `null`. |

The block adds three columns to the workflow output: `webhook_status_code`, `webhook_response` (first 2,000 characters) and `webhook_success`.

### Payload

```json theme={null}
{
  "event_id": "f7c2a4e0-9b5d-4a1f-8d2c-1e3b5f7a9c0d",
  "event": "outgoing_webhook.completed",
  "status": "success",
  "workflow_id": "3f8b2c1e-6d4a-4f9b-8e2c-1a5b7c9d0e3f",
  "run_id": "0b9d7c1e-2f4a-4e8b-9c3d-5a6f7e8d9c0b",
  "organization_id": "acme",
  "row_count": 95,
  "previous_block_id": "6f1c2a4e-1b7d-4c55-9a43-0d1e5f6a7b02",
  "previous_block_name": "lead_enrichment",
  "previous_block_number": 2,
  "completed_at": "2026-04-22T20:00:00Z",
  "duration_ms": 1234,
  "attempt": 1,
  "results_download_url": "https://api.sixtyfour.ai/storage/download/v1.eyJlIjoxNzkzNjQ5...",
  "ndjson_download_url": null,
  "results": [
    { "name": "Saarth Shah", "email": "saarth.work@example.com" }
  ]
}
```

| Field | Type | Description |
| - | - | - |
| `event_id` | string (UUID) | Unique per delivery and the same across its retries. Matches the `Sixtyfour-Event-Id` header. A block that runs again sends a new `event_id`; dedupe on `run_id` and `previous_block_id`. |
| `event` | string | Always `outgoing_webhook.completed`. |
| `status` | string | Always `success`. |
| `workflow_id` | string | The workflow definition ID. |
| `run_id` | string | The run ID. |
| `organization_id` | string | Your organization ID. |
| `row_count` | integer | Rows in the result, including rows that failed at an earlier step. |
| `previous_block_id` | string | ID of the block before the webhook block. |
| `previous_block_name` | string | Block type of the previous block, such as `lead_enrichment`. |
| `previous_block_number` | integer | Sequence number of the previous block. |
| `completed_at` | string (ISO 8601) | When this attempt was sent. |
| `duration_ms` | integer | Time spent in the webhook block. |
| `attempt` | integer | Delivery attempt, starting at `1`. |
| `results_download_url` | string \| null | Link to the previous block's CSV result file when `include_csv_download_link` is `true`. |
| `ndjson_download_url` | string \| null | Link to the previous block's NDJSON result file when `include_csv_download_link` is `true` and the run requested NDJSON results. |
| `results` | array \| null | Inline rows when the input is at most 200 rows and 512 KB; otherwise `null`. Rows are the ones entering the webhook block, without keys that start with `_`. |

Fetch both links with an `x-api-key` header from the run's organization within 15 minutes. For new links, call [Download results](https://docs.sixtyfour.ai/api-reference/workflows/workflows-execution.md#download-results) with the `run_id`. A CSV link returns [spreadsheet-safe](https://docs.sixtyfour.ai/api-reference/workflows/workflows-execution.md#spreadsheet-safe-csv) cells unless you add `?spreadsheet_safe=false`.

### Failed rows in the payload

The payload includes rows that failed at an earlier step, with `Failed` in the columns their failing step would have filled. The payload has no per-row status, so identify failed rows from the final result: wait for the run to reach a finished status and read its `Status` column. See [Failed rows](https://docs.sixtyfour.ai/api-reference/workflows/workflows-execution.md#failed-rows) and [Download results](https://docs.sixtyfour.ai/api-reference/workflows/workflows-execution.md#download-results). A run where every row fails ends as `failed`, and its results can still be downloaded.

## Delivery

### Headers

| Header | Value |
| - | - |
| `Content-Type` | `application/json` |
| `Sixtyfour-Signature` | `t=<unix_seconds>,v1=<hex>[,v1=<hex>]` |
| `Sixtyfour-Event-Id` | UUID per delivery, same across retries. Monitor notifications send their `event_group_id` or `run_id` |
| `Sixtyfour-Event-Type` | `task_type` for async jobs (omitted when it is null), `outgoing_webhook.completed` for the block, the `type` for monitor notifications |
| `Sixtyfour-Delivery-Attempt` | Attempt counter starting at `1` |

Sixtyfour sends the `Sixtyfour-*` headers only when your organization has a [signing secret](https://docs.sixtyfour.ai/api-reference/webhooks/signing-secrets.md). [Test deliveries](https://docs.sixtyfour.ai/guides/using-webhooks.md#test-deliveries) always add `Sixtyfour-Test` headers.

### Retries

| Setting | Value |
| - | - |
| Attempts | 5 (1 initial attempt and 4 retries) |
| Backoff | 1s, 2s, 4s, 8s between attempts |
| Timeout | 10 seconds per attempt for async jobs; `timeout_seconds` for the block |
| Success | Any `2xx` response |
| Redirects | Not followed. A `3xx` response counts as a failed attempt. |

If every attempt fails, the delivery is dropped. The job or run itself is unaffected, and its results stay available by polling.

### URL rules

Sixtyfour checks the destination before every attempt. URLs with credentials, `localhost`, `*.local` hosts, and hosts that resolve to private, loopback, link-local or other non-public IPs are rejected and not retried. A DNS lookup that fails counts as a failed attempt and is retried.

### Receiver checklist

* Return `2xx` within the timeout and process the payload asynchronously.
* Return `2xx` for events you ignore. Any other status triggers retries.
* Dedupe on the job or run, not only `event_id`: `task_id` for async jobs, `run_id` with `previous_block_id` for the workflow block, and `type` with `event_group_id` or `run_id` for monitor notifications. `event_id` covers only retries of one delivery, and monitor payloads have none. See the [receiver example](https://docs.sixtyfour.ai/guides/using-webhooks.md#handle-deliveries).
* Once signing is enabled, reject deliveries without a valid `Sixtyfour-Signature`.

## Polling fallback

Results stay available whether or not a webhook is delivered:

* Async jobs: `GET /job-status/{task_id}`
* Workflow runs: the status and download endpoints in [Workflow Execution](https://docs.sixtyfour.ai/api-reference/workflows/workflows-execution.md)

## Related

* [Signing Secrets](https://docs.sixtyfour.ai/api-reference/webhooks/signing-secrets.md)
* [Incoming Webhooks](https://docs.sixtyfour.ai/api-reference/webhooks/incoming.md)
* [Handling Errors](https://docs.sixtyfour.ai/api-reference/legacy/errors.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.