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 optionalwebhook_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
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. For rejected URLs, see Handling Errors.
Request
POST /find-email-async:
task_id immediately:
Payload
Result fields by endpoint
Contact lookups wrap records in
result.leads, even for one record; GET /job-status/{task_id} returns a single record as result (details). 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.
Job failures
Sixtyfour sends callbacks for completed jobs only; failed, cancelled and timed-out jobs send none. If no callback arrives by your deadline, pollGET /job-status/{task_id}.
Workflow Webhooks
Add anoutgoing_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 when no delivery arrives.
Block specs
The block adds three columns to the workflow output:
webhook_status_code, webhook_response (first 2,000 characters) and webhook_success.
Payload
Fetch both links with an
x-api-key header from the run’s organization within 15 minutes. For new links, call Download results with the run_id. A CSV link returns spreadsheet-safe cells unless you add ?spreadsheet_safe=false.
Failed rows in the payload
The payload includes rows that failed at an earlier step, withFailed 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 and Download results. A run where every row fails ends as failed, and its results can still be downloaded.
Delivery
Headers
Sixtyfour sends the
Sixtyfour-* headers only when your organization has a signing secret. Test deliveries always add Sixtyfour-Test headers.
Retries
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
2xxwithin the timeout and process the payload asynchronously. - Return
2xxfor events you ignore. Any other status triggers retries. - Dedupe on the job or run, not only
event_id:task_idfor async jobs,run_idwithprevious_block_idfor the workflow block, andtypewithevent_group_idorrun_idfor monitor notifications.event_idcovers only retries of one delivery, and monitor payloads have none. See the receiver example. - 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