409 webhook_endpoint_unverified - NoResponse docs

{
  "type": "https://docs.noresponse.org/problems/webhook-endpoint-unverified",
  "title": "Webhook endpoint unverified",
  "status": 409,
  "detail": "The endpoint is not verified; send endpoint.verification first.",
  "code": "webhook_endpoint_unverified",
  "request_id": "5e8be3a91fde9499f7ce48ae66290895"
}

{
  "type": "https://docs.noresponse.org/problems/webhook-endpoint-unverified",
  "title": "Webhook endpoint unverified",
  "status": 409,
  "detail": "The endpoint is not verified; send endpoint.verification first.",
  "code": "webhook_endpoint_unverified",
  "request_id": "5e8be3a91fde9499f7ce48ae66290895"
}

HTTP 409 Not retryable

Why

An endpoint is not verified until it echoes a verification challenge. The same code answers for an endpoint that NoResponse disabled after 72 hours of failed deliveries.

What to do

Send endpoint.verification with the same call, and answer the challenge. The endpoint becomes verified when it echoes the challenge.

In the SDKs

The Node and Python SDKs raise ConflictError. The Go SDK returns *apierrors.ConflictError, which you match with errors.As.

{
  "type": "https://docs.noresponse.org/problems/webhook-endpoint-unverified",
  "title": "Webhook endpoint unverified",
  "status": 409,
  "detail": "The endpoint is not verified; send endpoint.verification first.",
  "code": "webhook_endpoint_unverified",
  "request_id": "5e8be3a91fde9499f7ce48ae66290895"
}

Every error has this shape. Errors and limits lists every code.