> ## 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.

# List form notifications

> GET /forms/notification/

Lists the account's configured form report notifications — scheduled email (and optionally Slack) digests of new form responses.

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

<RequestExample>
  ```bash cURL theme={null}
  curl --request GET \
    --url 'https://api.scanova.io/forms/notification/' \
    --header 'Authorization: YOUR_API_KEY'
  ```
</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": true,
      "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-08T10:05:00+05:30"
    }
  ]
  ```
</ResponseExample>

The response is a flat array, not paginated.

## Related

* [Create a form notification](/api-reference/management-api/form-notifications/create) — add one.
* [List form notification frequencies](/api-reference/management-api/form-notifications/frequency) — valid `frequency` values.
* [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 GET /forms/notification/
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/:
    get:
      summary: List form notifications
      operationId: listManagedFormNotifications
      responses:
        '200':
          description: List of form report notifications.
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.

````