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

# 更新潜在客户列表 webhook

> PATCH /lead/{lead_id}/webhook/{pk}/

更新潜在客户列表 webhook 的 URL。

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

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

<ParamField path="lead_id" type="string" required>
  潜在客户列表的 `lead_id`。
</ParamField>

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

<ParamField body="url" type="string" required>
  webhook 的新目标 URL。
</ParamField>

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

<ResponseExample>
  ```json 200 theme={null}
  { "id": 7, "url": "https://example.com/new-lead-webhook", "created": "2026-09-08T10:00:00+05:30", "modified": "2026-09-08T11:00:00+05:30" }
  ```
</ResponseExample>

同时支持 `PUT` 和 `PATCH`。如果 `lead_id` 不属于此账户，或 `pk` 不是此潜在客户列表的 webhook，则返回 `404`。

## 相关内容

* [获取潜在客户列表 webhook](/zh/api-reference/management-api/lead-webhooks/retrieve) —— 更新前查看。
* [删除潜在客户列表 webhook](/zh/api-reference/management-api/lead-webhooks/delete) —— 将其彻底移除。
* [管理 API 概述](/zh/api-reference/management-api/overview) —— 此端点所属的身份验证方案和配额体系。


## OpenAPI

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

````