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

# 创建线索列表

> POST /lead/

线索列表是 Scanova 最初的线索收集功能——一个附加在二维码落地页上的表单定义（`data`）。在此列出或创建线索列表。

<Warning>
  线索列表是一项**旧版**功能。Scanova 仪表盘现在会将新的线索收集使用场景引导至[表单](/zh/api-reference/management-api/forms/create)，后者以更强大的构建器覆盖了同样的"从二维码扫描中收集访客数据"使用场景。现有的线索列表会继续正常工作，本端点也不受影响，但除非您确实需要管理已存在的线索列表，否则请针对表单构建新的集成。
</Warning>

<Note>
  需要一个拥有 `MANAGEMENT_API`（或 `MANAGEMENT_API_SANDBOX`）配额的 Management API 密钥，以原始 `Authorization` 请求头的值发送——参见 [Management API 概览](/zh/api-reference/management-api/overview)。
</Note>

<RequestExample>
  ```bash cURL theme={null}
  curl --request POST \
    --url 'https://management.scanova.io/lead/' \
    --header 'Authorization: YOUR_API_KEY' \
    --header 'Content-Type: application/json' \
    --data '{
      "name": "Trade Show Signup",
      "data": "{\"fields\":[{\"type\":\"email\",\"label\":\"Email\",\"required\":true}]}"
    }'
  ```
</RequestExample>

<ResponseExample>
  ```json 201 theme={null}
  {
    "id": 205,
    "lead_id": "L9c2f4a1e",
    "name": "Trade Show Signup",
    "created": "2026-08-16T20:44:51.008000+05:30",
    "is_active": true,
    "usage_count": 0,
    "entries_count": 0,
    "linked_qrs": [],
    "modified": "2026-08-16T20:44:51.008000+05:30",
    "data": "{\"fields\":[{\"type\":\"email\",\"label\":\"Email\",\"required\":true}]}",
    "webhooks": []
  }
  ```
</ResponseExample>

<ParamField body="name" type="string" required>
  线索列表名称，最多 128 个字符。
</ParamField>

<ParamField body="data" type="string" required>
  一个 JSON 编码的字符串（而非原始对象），用于描述线索表单的字段。会依据仪表盘线索列表构建器所使用的同一套线索表单模式进行校验——格式错误的 JSON 或违反模式的内容会在 `data` 字段下返回 400 错误。
</ParamField>

<ParamField body="is_active" type="boolean" default="true">
  该表单是否在落地页上渲染。
</ParamField>

<Note>
  响应中包含 `data` 和 `webhooks`（一份 `{id, url, created, modified}` 形式的通知 Webhook 列表）——这些字段仅出现在创建/获取所返回的详情数据结构中，不出现在上方的列表端点中。
</Note>

## 相关内容

* [列出线索列表](/zh/api-reference/management-api/leads/list) — 同一端点的另一个操作。
* [表单管理](/zh/api-reference/management-api/forms/create) —— 当前推荐的线索收集构建器，本旧版功能正被引导迁移至此。
* [Management API 概览](/zh/api-reference/management-api/overview) —— 本端点所属的身份验证方案与配额架构。


## OpenAPI

````yaml api-reference/openapi/management-api.json POST /lead/
openapi: 3.1.0
info:
  title: Scanova Management API (v2)
  description: >-
    The complete Scanova Management API — every endpoint available at
    management.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://management.scanova.io
    description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
  - apiKeyAuth: []
paths:
  /lead/:
    post:
      summary: Create a lead list
      operationId: createManagedLeadList
      responses:
        '201':
          description: Lead list created
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. management.scanova.io) — the same key sent to
        the regular API host will not authenticate.

````