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

# Link QR Codes to a lead list

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

Sets the full set of QR Codes attached to a lead list.

<Warning>
  This call **replaces** the entire link set — every QR Code currently linked to this lead list is unlinked first, then exactly the QR Codes you send are linked. To keep an existing link, include its `qrid` in the request.
</Warning>

<Note>
  Requires a Management API key with `MANAGEMENT_API` (or `MANAGEMENT_API_SANDBOX`) quota, sent as the raw `Authorization` header value — see the [Management API overview](/api-reference/management-api/overview).
</Note>

<ParamField path="lead_id" type="string" required>
  The lead list's `lead_id`.
</ParamField>

The request body is a **raw JSON array** of QR `qrid` strings — not wrapped in an object.

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

Only dynamic QR Codes (`qr_type: "dy"`) owned by this account can be linked — a `qrid` for a static or foreign QR Code is silently dropped from the target set rather than raising an error. If a target QR Code was previously attached to a Form, that Form link is removed, since a QR Code can only be attached to one lead-capture resource at a time.

## Related

* [Retrieve a lead list](/api-reference/management-api/leads/retrieve) — view the current link set.
* [Management API overview](/api-reference/management-api/overview) — the auth scheme and quota architecture this endpoint is part of.


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

````