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

# 更新潜在客户列表

> PATCH /lead/{lead_id}/

更新潜在客户列表的名称、表单定义或激活状态。

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

```
PUT   https://api.scanova.io/lead/{lead_id}/
PATCH https://api.scanova.io/lead/{lead_id}/
```

<ParamField path="lead_id" type="string" required>
  潜在客户列表的 `lead_id`。不可变 —— 无法通过此端点更改。
</ParamField>

<ParamField body="name" type="string">
  潜在客户列表名称，最多 128 个字符。
</ParamField>

<ParamField body="data" type="string">
  描述潜在客户表单字段的 JSON 编码字符串（不是原始对象）。会根据创建时使用的相同架构进行验证 —— 格式错误的 JSON 或架构违规会在 `data` 下返回 `400`。
</ParamField>

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

<RequestExample>
  ```bash cURL theme={null}
  curl --request PATCH \
    --url 'https://api.scanova.io/lead/L9c2f4a1e/' \
    --header 'Authorization: YOUR_API_KEY' \
    --header 'Content-Type: application/json' \
    --data '{ "is_active": false }'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": 205,
    "lead_id": "L9c2f4a1e",
    "name": "Trade Show Signup",
    "is_active": false,
    "usage_count": 2,
    "entries_count": 14,
    "linked_qrs": [
      { "qr_code__id": 88, "qr_code__qrid": "Q7f3a", "qr_code__name": "Booth QR", "qr_code__qr_type": "dy" }
    ],
    "linked_qrs_count": 1,
    "created": "2026-08-16T20:44:51.008000+05:30",
    "modified": "2026-09-08T10:12:00.000000+05:30",
    "data": "{\"fields\":[{\"type\":\"email\",\"label\":\"Email\",\"required\":true}]}",
    "webhooks": []
  }
  ```
</ResponseExample>

同时支持 `PUT` 和 `PATCH`。如果 `lead_id` 不属于此账户，则返回 `404`。

## 相关内容

* [获取潜在客户列表](/zh/api-reference/management-api/leads/retrieve) —— 更新前查看当前值。
* [删除潜在客户列表](/zh/api-reference/management-api/leads/delete) —— 永久删除它。
* [管理 API 概述](/zh/api-reference/management-api/overview) —— 此端点所属的身份验证方案和配额体系。


## OpenAPI

````yaml api-reference/openapi/management-api.json PATCH /lead/{lead_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:
  /lead/{lead_id}/:
    patch:
      summary: Update a lead list
      operationId: partialUpdateManagedLeadList
      responses:
        '200':
          description: Lead list updated.
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.

````