Apideck webhooks can be created disabled: check status after subscribing

TL;DR: Each delivery also has a hard 60-second timeout; slow endpoints get logged as failed (statuscode 0) and retried. ## What to do When an Apideck webhook silently never fires, don't debug your handler first: GET /webhook/webhooks and check the subscription's status. Web (Apideck official OpenAPI spec, webhook.yml): documents that creating a webhook subscription triggers synchronous deliveryurl validation: Apideck POSTs an HMAC-signed request to your URL at creation time.

Web (Apideck official OpenAPI spec, webhook.yml): documents that creating a webhook subscription triggers synchronous deliveryurl validation: Apideck POSTs an HMAC-signed request to your URL at creation time. If validation fails (network error, timeout, non-2xx response), the webhook is STILL created but with status disabled and disabledreason deliveryurlvalidationfailed. Each delivery also has a hard 60-second timeout; slow endpoints get logged as failed (statuscode 0) and retried.

What to do

When an Apideck webhook silently never fires, don't debug your handler first: GET /webhook/webhooks and check the subscription's status. If it says disabled with disabledreason deliveryurlvalidationfailed, your endpoint failed the synchronous validation POST at creation time (timeout, non-2xx, network error). Fix the endpoint and re-enable the webhook. Separately, keep your handler fast: Apideck gives each delivery 60 seconds, then marks it failed and retries. Acknowledge with HTTP 2xx immediately and do the real work asynchronously, or you'll get duplicate deliveries from the retry policy.

When to use

You hit exactly this: Apideck webhooks can be created disabled: check status after subscribing in Apideck webhooks can be created disabled.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Apideck webhooks can be created disabled.

Web (Apideck official OpenAPI spec, webhook.yml): documents that creating a webhook subscription triggers synchronous deliveryurl validation: Apideck POSTs an HMAC-signed request to your URL at creation time. If validation fails (network error, timeout, non-2xx response), the webhook is STILL created but with status disabled and disabledreason deliveryurlvalidationfailed. Each delivery also has a hard 60-second timeout; slow endpoints get logged as failed (statuscode 0) and retried.

Verified answer: When an Apideck webhook silently never fires, don't debug your handler first: GET /webhook/webhooks and check the subscription's status. If it says disabled with disabledreason deliveryurlvalidationfailed, your endpoint failed the synchronous validation POST at creation time (timeout, non-2xx, network error). Fix the endpoint and re-enable the webhook. Separately, keep your handler fast: Apideck gives each delivery 60 seconds, then marks it failed and retries. Acknowledge with HTTP 2xx immediately and do the real work asynchronously, or you'll get duplicate deliveries from the retry policy.

Source: https://raw.githubusercontent.com/apideck-libraries/openapi-specs/main/webhook.yml