---
title: "Enable a webhook subscription"
method: POST
path: "/v3/webhooks/{id}/enable"
tags: ["Webhooks"]
---

# Enable a webhook subscription

`POST /v3/webhooks/{id}/enable`

<small>_Requires the `webhooks:operate` scope (or a broader one that includes it)._</small>

Resumes a paused subscription. Idempotent — calling on an already-enabled
subscription still returns `204`. Use this dedicated endpoint rather than
`PUT` to toggle the paused state (`PUT` does not accept the `enabled` flag).

When the active-subscriptions limit has been reached, returns `409 Conflict`
with `code: webHook.limitReached`.

## Path parameters

- `id` integer, required

## Response `204`

Subscription is enabled (or was already enabled). The response body is empty.

- unknown

## Other responses

- `400` — Invalid `id` parameter.
- `401` — Unauthorized. The response body is empty; check the `WWW-Authenticate` header for the expected scheme.
- `404` — Subscription not found or not owned by the caller.
- `409` — Enabling would exceed the active webhook-subscription limit for the user.
- `429` — Too Many Requests

---

[API](https://skmtc.net/reply/apis/reply-api.md) · [All operations](https://skmtc.net/reply/apis/reply-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/reply/reply-api/revisions/1c3d32eaf95e/schema)