> ## 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 your account

> POST /qr/link/

Claims QR Codes that were created before login and assigns them to the authenticated account.

```
POST   https://api.scanova.io/qr/link/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField body="qr" type="array" required>
  A non-empty list of `qrid` values to claim.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://api.scanova.io/qr/link/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -H "Content-Type: application/json" \
    -d '{
        "qr": [
            "Qa1b2c3d4e5f6g7h8"
        ]
    }'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 OK theme={null}
  "success"
  ```
</ResponseExample>

<Note>
  This exists for the sign-up flow, where a visitor builds a QR Code anonymously on the public API and then registers. Since QR Code creation on the Management API host always requires an API key, QR Codes created **through this API** are already owned and never need linking.
</Note>

## Related

* [Create a QR Code](/api-reference/management-api/qr/create) — creation on this host is always owned, so it needs no linking.
* [List QR Codes](/api-reference/management-api/qr/list) — confirm the claimed QR Codes now appear in the account.
* [QR Manager overview](/api-reference/management-api/qr/overview) — the quotas, role permissions, and Trash model shared by every endpoint in this module.
* [Management API overview](/api-reference/management-api/overview) — the auth scheme and quota rules that apply to this endpoint.


## OpenAPI

````yaml api-reference/openapi/management-api.json POST /qr/link/
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:
  /qr/link/:
    post:
      summary: Link anonymously-created QR codes to the caller
      description: >-
        Claims QR codes that were created before login (anonymously, on the
        public API) and assigns them to the now-authenticated account.
      operationId: linkAnonymousQrCodes
      requestBody:
        content:
          application/json:
            example:
              qr:
                - Qa1b2c3d4e5f6g7h8
                - Qb2c3d4e5f6g7h8i9
      responses:
        '200':
          description: QR codes linked.
          content:
            application/json:
              example: success
        '400':
          description: '`qr` empty, or none of the given identifiers are claimable.'
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.

````