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

# Retrieve / update / delete a Slack notification rule

> GET, PATCH, PUT, DELETE /webhook/slack/notification-rule/{id}/

Manages a single Slack notification rule. Both `PATCH` and `PUT` are supported.

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

<ParamField path="id" type="integer" required>
  Rule id, from [List Slack notification rules](/api-reference/management-api/integrations/slack-rules-list-create).
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl --request DELETE \
    --url 'https://api.scanova.io/webhook/slack/notification-rule/6/' \
    --header 'Authorization: YOUR_API_KEY'
  ```
</RequestExample>

`404` if `id` isn't a rule on this account's connected workspace.

## Related

* [List / create Slack notification rules](/api-reference/management-api/integrations/slack-rules-list-create)
* [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/{id}/
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/{id}/:
    get:
      summary: Retrieve a Slack notification rule
      operationId: getManagedSlackRule
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: integer
      responses:
        '200':
          description: One rule.
          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'
        '404':
          description: No rule with this id owned by this account.
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.

````