> ## 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/frequency/

列出潜在客户通知允许的 `frequency` 值。

<Note>
  仅需要账户身份验证 —— 与其余潜在客户通知端点不同，此端点不应用 `MANAGEMENT_API` 配额检查。
</Note>

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

<ResponseExample>
  ```json 200 theme={null}
  [
    { "key": 1, "value": "Per Lead" },
    { "key": 2, "value": "Daily" },
    { "key": 3, "value": "Once a Week" },
    { "key": 4, "value": "Once a Month" }
  ]
  ```
</ResponseExample>

创建或更新通知时，使用 `key` 作为 `frequency` 值。

## 相关内容

* [创建潜在客户通知](/zh/api-reference/management-api/lead-notifications/create) —— 设置 `frequency` 的位置。
* [管理 API 概述](/zh/api-reference/management-api/overview) —— 此端点所属的身份验证方案和配额体系。


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /lead/notification/frequency/
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/frequency/:
    get:
      summary: List lead notification frequencies
      operationId: listManagedLeadNotificationFrequencies
      responses:
        '200':
          description: Allowed frequency values.
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.

````