> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanova.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Update a form notification

> PATCH /forms/notification/{pk}/

Updates a form report notification.

<Note>
  Requires a Management API key with `MANAGEMENT_API` (or `MANAGEMENT_API_SANDBOX`) quota, and the `LEAD_GENERATION_EMAIL_REPORT_CAN_CREATE_UPDATE` permission, sent as the raw `Authorization` header value — see the [Management API overview](/api-reference/management-api/overview).
</Note>

```
PUT   https://api.scanova.io/forms/notification/{pk}/
PATCH https://api.scanova.io/forms/notification/{pk}/
```

<ParamField path="pk" type="integer" required>
  The notification's `id`.
</ParamField>

<ParamField body="name" type="string">
  Internal name.
</ParamField>

<ParamField body="to" type="string">
  Recipient email address(es).
</ParamField>

<ParamField body="cc" type="string">
  CC email address(es).
</ParamField>

<ParamField body="bcc" type="string">
  BCC email address(es).
</ParamField>

<ParamField body="frequency" type="integer">
  One of the `key` values from [List form notification frequencies](/api-reference/management-api/form-notifications/frequency).
</ParamField>

<ParamField body="form_ids" type="array">
  Replaces the full set of `form_id`s this notification reports on.
</ParamField>

<ParamField body="is_active" type="boolean">
  Enable or disable the notification.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl --request PATCH \
    --url 'https://api.scanova.io/forms/notification/21/' \
    --header 'Authorization: YOUR_API_KEY' \
    --header 'Content-Type: application/json' \
    --data '{ "is_active": false }'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": 21,
    "name": "Weekly Booth Signups",
    "to": "sales@example.com",
    "cc": "manager@example.com",
    "bcc": null,
    "frequency": 3,
    "frequency_display": "Once a Week",
    "form_list": [{ "form_name": "Booth Signup", "form_id": "F8a9b0c1d2e3f4g5h" }],
    "is_active": false,
    "slack_workspace": null,
    "slack_channel_ids": null,
    "created_by": { "id": 41, "email": "you@example.com" },
    "created": "2026-09-08T10:05:00+05:30",
    "modified": "2026-09-08T11:30:00+05:30"
  }
  ```
</ResponseExample>

Both `PUT` and `PATCH` are supported. `404` if `pk` isn't a notification owned by this account.

## Related

* [Retrieve a form notification](/api-reference/management-api/form-notifications/retrieve) — view before updating.
* [Delete a form notification](/api-reference/management-api/form-notifications/delete) — remove it entirely.
* [Management API overview](/api-reference/management-api/overview) — the auth scheme and quota architecture this endpoint is part of.


## OpenAPI

````yaml api-reference/openapi/management-api.json PATCH /forms/notification/{pk}/
openapi: 3.1.0
info:
  title: Scanova Management API (v2)
  description: >-
    The complete Scanova Management API — every endpoint available at
    api.scanova.io (QR codes, folders, tags, leads, forms, analytics, plans,
    shared users & roles), plus the token-creation and usage-stats endpoints
    used to authenticate against it. Every path and request/response shape below
    was verified live against a real API key and the actual running backend
    (Phase 7, 2026-08-16) — not guessed from reading urls.py alone.
  version: 2.0.0
servers:
  - url: https://api.scanova.io
    description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
  - apiKeyAuth: []
paths:
  /forms/notification/{pk}/:
    patch:
      summary: Update a form notification
      operationId: partialUpdateManagedFormNotification
      responses:
        '200':
          description: Notification updated.
components:
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        Send your Management API key as the raw value of the Authorization
        header — no "Bearer " or "Token " prefix, and no other characters.
        Example: `Authorization: 401f7ac837da42b97f613d789819ff93537bee6a`. A
        header containing more than one space-separated part is rejected
        outright. Requests also require the request's Host header to be the
        management API host (e.g. api.scanova.io) — the same key sent to the
        regular API host will not authenticate.

````