endpoint_disabled
This code is registered so the envelope contract and its
docs_url
anchor stay stable, but no route currently emits it — a disabled
endpoint simply stops receiving deliveries, and the affected events are
recorded as permanently failed with an “Endpoint inactive” reason. Do
not write receiver logic that waits for this response.
An endpoint gets disabled in two ways:
- Automatically, and only after five consecutive permanently
failed deliveries.
disabledReasonis free-form prose carrying the streak threshold, today"repeated_failures (>= 5 consecutive deliveries)"; the threshold is interpolated from the retry schedule, so match therepeated_failuresprefix rather than the full string. A failed DNS/SSRF re-check counts as one failed attempt feeding that streak — it is not a disable trigger of its own. - Manually, from the dashboard or
PATCH /v1/webhook-endpoints/{id}withisActive: false.
2xx within 10 seconds),
then re-enable the endpoint via
PATCH /v1/webhook-endpoints/{endpointId} with isActive: true or from
the dashboard. See Webhooks § Delivery and retries.