> ## 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 / create Slack notification rules

> GET, POST /webhook/slack/notification-rule/

A **notification rule** picks which account events (lead capture, QR Code scans, form responses, etc.) post to which Slack channels.

<Note>
  Requires the account's `INTEGRATION_SLACK` quota.
</Note>

<ParamField body="name" type="string" required>
  Rule display name.
</ParamField>

<ParamField body="lead_capture" type="boolean">
  Notify on a new lead capture.
</ParamField>

<ParamField body="qr_scan" type="boolean">
  Notify on a QR Code scan.
</ParamField>

<ParamField body="form_response" type="boolean">
  Notify on a new form response.
</ParamField>

<ParamField body="qr_created" type="boolean">
  Notify when a QR Code is created.
</ParamField>

<ParamField body="qr_deleted" type="boolean">
  Notify when a QR Code is deleted.
</ParamField>

<ParamField body="page_created" type="boolean">
  Notify when a landing page is created.
</ParamField>

<ParamField body="page_deleted" type="boolean">
  Notify when a landing page is deleted.
</ParamField>

<ParamField body="shared_user_added" type="boolean">
  Notify when a shared user is added.
</ParamField>

<ParamField body="shared_user_deleted" type="boolean">
  Notify when a shared user is removed.
</ParamField>

<ParamField body="custom_domain_added" type="boolean">
  Notify when a custom domain is connected.
</ParamField>

<ParamField body="custom_domain_deleted" type="boolean">
  Notify when a custom domain is removed.
</ParamField>

<ParamField body="lead_list_ids" type="array">
  Restrict `lead_capture` notifications to these lead list ids. Omit/empty for all lists.
</ParamField>

<ParamField body="channel_ids" type="array" required>
  Slack channel ids (from [List Slack channels](/api-reference/management-api/integrations/slack-channels)) to post to.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl --request POST \
    --url 'https://api.scanova.io/webhook/slack/notification-rule/' \
    --header 'Authorization: YOUR_API_KEY' \
    --header 'Content-Type: application/json' \
    --data '{
      "name": "New leads",
      "lead_capture": true,
      "lead_list_ids": [12],
      "channel_ids": ["C0123ABC"]
    }'
  ```
</RequestExample>

<ResponseExample>
  ```json 201 theme={null}
  {
    "id": 6,
    "name": "New leads",
    "lead_capture": true,
    "qr_scan": false,
    "form_response": false,
    "qr_created": false,
    "qr_deleted": false,
    "page_created": false,
    "page_deleted": false,
    "shared_user_added": false,
    "shared_user_deleted": false,
    "custom_domain_added": false,
    "custom_domain_deleted": false,
    "lead_list_ids": [12],
    "channel_ids": ["C0123ABC"],
    "created": "2026-09-09T08:00:00+05:30",
    "modified": "2026-09-09T08:00:00+05:30"
  }
  ```
</ResponseExample>

If there's no connected Slack workspace, `GET` returns an empty list rather than `404` — only actions that need to write against the workspace (`POST`) raise `404`.

## Related

* [Retrieve / update / delete a Slack notification rule](/api-reference/management-api/integrations/slack-rule-retrieve)
* [List Slack channels](/api-reference/management-api/integrations/slack-channels)
* [Slack connection status](/api-reference/management-api/integrations/slack-status)
* [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 /webhook/slack/notification-rule/
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:
  /webhook/slack/notification-rule/:
    get:
      summary: List Slack notification rules
      operationId: listManagedSlackRules
      responses:
        '200':
          description: Rules for the connected workspace (empty list if none connected).
          content:
            application/json:
              example:
                - id: 6
                  name: New leads
                  lead_capture: true
                  qr_scan: false
                  form_response: false
                  qr_created: false
                  qr_deleted: false
                  page_created: false
                  page_deleted: false
                  shared_user_added: false
                  shared_user_deleted: false
                  custom_domain_added: false
                  custom_domain_deleted: false
                  lead_list_ids:
                    - 12
                  channel_ids:
                    - C0123ABC
                  created: '2026-09-09T08:00:00+05:30'
                  modified: '2026-09-09T08:00:00+05:30'
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.

````