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

# 获取潜在客户通知

> GET /lead/notification/{pk}/

获取单个潜在客户报告通知。

<Note>
  需要具有 `MANAGEMENT_API`（或 `MANAGEMENT_API_SANDBOX`）配额的管理 API 密钥，作为原始 `Authorization` 标头值发送 —— 参见[管理 API 概述](/zh/api-reference/management-api/overview)。
</Note>

<ParamField path="pk" type="integer" required>
  通知的 `id`。
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl --request GET \
    --url 'https://api.scanova.io/lead/notification/12/' \
    --header 'Authorization: YOUR_API_KEY'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": 12,
    "name": "Weekly Trade Show Report",
    "to": "sales@example.com",
    "cc": "manager@example.com",
    "bcc": null,
    "frequency": 3,
    "frequency_display": "Once a Week",
    "lead_list": [{ "lead_list_name": "Trade Show Signup", "lead_list_id": "L9c2f4a1e" }],
    "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>

如果 `pk` 不是调用用户创建的通知，则返回 `404`。

## 相关内容

* [列出潜在客户通知](/zh/api-reference/management-api/lead-notifications/list) —— 查找 `id`。
* [更新潜在客户通知](/zh/api-reference/management-api/lead-notifications/update) —— 更改其设置。
* [管理 API 概述](/zh/api-reference/management-api/overview) —— 此端点所属的身份验证方案和配额体系。


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /lead/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:
  /lead/notification/{pk}/:
    get:
      summary: Retrieve a lead notification
      operationId: retrieveManagedLeadNotification
      responses:
        '200':
          description: Notification detail.
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.

````