> ## 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 /forms/{form_id}/link-qrs/

设置链接到表单的完整 QR 码集合。

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

<Note>
  仅需要账户身份验证 —— 与此资源的大多数写入端点不同，此处不应用 `MANAGEMENT_API` 配额或 `LEAD_GENERATION_CAN_EDIT` 权限检查。
</Note>

<ParamField path="form_id" type="string" required>
  表单的 `form_id`。
</ParamField>

<ParamField body="qr_ids" type="array" required>
  QR `qrid` 字符串数组 —— 表单之后应链接到的完整 QR 码集合。
</ParamField>

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

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": 376,
    "form_id": "F8a9b0c1d2e3f4g5h",
    "name": "Booth Signup",
    "created": "2026-08-16T20:46:12.554000+05:30",
    "is_active": true,
    "usage_count": 2,
    "linked_qrs": [
      { "qr_code__id": 9021, "qr_code__qrid": "Q07afe81aa0034c01", "qr_code__name": "docs-v2-first-qr-code", "qr_code__qr_type": "dy" }
    ],
    "entries_count": 3,
    "conversion": 12.5,
    "modified": "2026-09-08T10:12:00.000000+05:30"
  }
  ```
</ResponseExample>

只有此账户拥有的动态 QR 码（`qr_type: "dy"`）才能被链接 —— 静态或不属于此账户的 QR 码的 `qrid` 会被静默地从目标集合中删除，而不会引发错误。

## 相关内容

* [获取表单](/zh/api-reference/management-api/forms/retrieve) —— 查看当前链接集合。
* [创建表单](/zh/api-reference/management-api/forms/create) —— 在创建时通过 `qr_id` 附加一个 QR 码。
* [管理 API 概述](/zh/api-reference/management-api/overview) —— 此端点所属的身份验证方案和配额体系。


## OpenAPI

````yaml api-reference/openapi/management-api.json POST /forms/{form_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:
  /forms/{form_id}/link-qrs/:
    post:
      summary: Link QR codes to a form
      operationId: linkQrsToManagedForm
      responses:
        '200':
          description: Form 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: 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.

````