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

# 将 QR 码链接到潜在客户列表

> POST /lead/{lead_id}/link-qrs/

设置链接到潜在客户列表的完整 QR 码集合。

<Warning>
  此调用会**替换**整个链接集合 —— 当前链接到此潜在客户列表的每个 QR 码都会先被取消链接，然后再精确链接您发送的 QR 码。要保留现有链接，请在请求中包含其 `qrid`。
</Warning>

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

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

请求体是一个**原始 JSON 数组**，包含 QR `qrid` 字符串 —— 不包裹在对象中。

<RequestExample>
  ```bash cURL theme={null}
  curl --request POST \
    --url 'https://api.scanova.io/lead/L9c2f4a1e/link-qrs/' \
    --header 'Authorization: YOUR_API_KEY' \
    --header 'Content-Type: application/json' \
    --data '["Q7f3a", "Qa91d"]'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 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": 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,
    "modified": "2026-09-08T10:12:00.000000+05:30"
  }
  ```
</ResponseExample>

只有此账户拥有的动态 QR 码（`qr_type: "dy"`）才能被链接 —— 静态或不属于此账户的 QR 码的 `qrid` 会被静默地从目标集合中删除，而不会引发错误。如果目标 QR 码此前附加到某个表单，该表单链接将被移除，因为一个 QR 码一次只能附加到一个潜在客户捕获资源。

## 相关内容

* [获取潜在客户列表](/zh/api-reference/management-api/leads/retrieve) —— 查看当前链接集合。
* [管理 API 概述](/zh/api-reference/management-api/overview) —— 此端点所属的身份验证方案和配额体系。


## OpenAPI

````yaml api-reference/openapi/management-api.json POST /lead/{lead_id}/link-qrs/
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}/link-qrs/:
    post:
      summary: Link QR codes to a lead list
      operationId: linkQrsToManagedLeadList
      responses:
        '200':
          description: Lead list with the updated link set.
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: YOUR_API_KEY`. 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.

````