WEBHOOK_NOT_CONFIGURED
The bulk run has no webhook URL to deliver to
A redelivery of the completion webhook was asked for a run created without a `webhook_url`, so there is no address to post to and no secret to sign with.
- http status
- 409
- credits
- Nothing is billed for a failed request.
What it means
A webhook URL is set once, when the run is created, and the signing secret is minted with it and returned once. A run started without one was never going to be posted about, so there is no first delivery to repeat and nothing this call could invent — a URL supplied now would be an unauthenticated request to send a signed POST at an arbitrary address.
Nothing is delivered and nothing is charged.
What to do
Download the results instead (`GET /api/v1/email/bulk/{jobId}/results` and its twins), and pass `webhook_url` when you create the next run so its finish announces itself.
Example response
{
"success": false,
"error": {
"code": "WEBHOOK_NOT_CONFIGURED",
"message": "This run was created without a webhook URL, so there is no completion webhook to send.",
"request_id": "req_01m1kgdm4xngzmbmff68g94w0c"
}
}Every error carries the request_id also sent in the X-Request-Id header; quote it when writing to support.
Related
- RESULTS_NOT_READY · the bulk job has not finished yet
- JOB_ALREADY_FINISHED · the bulk job cannot be cancelled any more
- JOB_CANCELLED · the bulk job was cancelled before producing results
- JOB_FAILED · the bulk job failed before producing results
- JOB_NOT_RESUMABLE · the bulk job is not in a state a resume can recover
- JOB_INPUT_EXPIRED · the list the bulk job ran on is no longer stored
- JOB_NOT_FINISHED · the bulk run has not finished, so there is no completion webhook to send
- IDEMPOTENCY_KEY_REUSED · the Idempotency-Key was already used for a different bulk request
- All error codes
- Verdicts and the risk score
- API reference
markdown version: /docs/errors/WEBHOOK_NOT_CONFIGURED.md