Skip to main content

Enable Webhook Subscription

POST 

/api/webhook-subscriptions/:id/enable

Turn a disabled subscription back on and return it in its new state. Idempotent — calling it on a subscription that is already active returns 200 with the row unchanged.

Required scope: webhooks:manage

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

Re-enabling clears disabled_reason and resets failure_count to 0, so a subscription that was auto-disabled at the consecutive-failure cap gets a full budget of retries rather than tripping again on its next single failure. The target URL is re-checked against the SSRF guard at this point, because DNS may have been re-pointed at a private address since the subscription was created.

Returns 422 when the subscription cannot be re-enabled: either the reason it was disabled is not user-recoverable (revoked — the connected app it was created under no longer has access, so the user must reconnect that app instead), or the target URL no longer passes the SSRF guard. can_reenable on the subscription tells you in advance which case you are in.

Requires the webhooks:manage scope.

Subscriptions are scoped to the tenant, not to the user who created them: any caller holding webhooks:manage on the tenant may act on any subscription it can see in the list. An id that does not exist on the tenant returns 404.

Request

Responses

OK

Response Headers
    Content-Type