---
title: "Turn form-reply capture on or off for a site"
method: PATCH
path: "/sites/{id}/form-capture"
tags: ["Sites"]
---

# Turn form-reply capture on or off for a site

`PATCH /sites/{id}/form-capture`

## Request

- Base URL: `https://api.nippy.host`
- URL: `https://api.nippy.host/sites/{id}/form-capture`
- Auth: `bearer` (a scheme the document does not define)

Persists the owner preference and re-publishes the KV record so the worker starts or stops injecting the capture script (and accepting submission beacons) on the next request. Available on every plan — the plan gates reading replies, never stopping their capture.

## Path parameters

- `id` string, required

## Request body

- UpdateSiteFormCaptureDto
  - `formCaptureEnabled` boolean, required: When true, the worker injects the form-capture script and accepts submission beacons for this site. When false, capture stops entirely on the next request and no new replies are stored.

## Response `200`

- APISiteFormCaptureResponse
  - `id` string, required: Site UUID
  - `formCaptureEnabled` boolean, required: Whether form-reply capture is enabled for this site.

## Other responses

- `400`: Invalid request body
- `401`: Not authenticated
- `403`: You do not own this site
- `404`: Site not found

---

[API](https://skmtc.dev/nippy/apis/nippy-backend-api.md) · [All operations](https://skmtc.dev/nippy/apis/nippy-backend-api/llms.txt) · [OpenAPI document](https://skmtc.dev/nippy/apis/nippy-backend-api/revisions/7ab23f040a55?raw)