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

# List / attach QR Codes

> GET, POST /web-tracking/sites/{site_id}/qrs/

Lists the QR Codes attached to a tracking site, or attaches a new one. Attaching links the tracking site to a QR Code's underlying dynamic URL object so that scans/visits can be correlated with the site's browser/server events.

<Note>
  Requires the account's `CONVERSION_TRACKING` quota. A `dynamic_url_object` can be attached to at most one tracking site at a time (`OneToOneField`) — attaching one already attached elsewhere returns `400`.
</Note>

<ParamField path="site_id" type="integer" required>
  Tracking site ID.
</ParamField>

<ParamField body="dynamic_url_object" type="integer" required>
  The `id` of the QR Code's dynamic URL object (from its `dynamic_url_object.id`, not the QR's own `id`/`qrid`).
</ParamField>

<RequestExample>
  ```bash cURL List theme={null}
  curl --request GET \
    --url 'https://api.scanova.io/web-tracking/sites/7/qrs/' \
    --header 'Authorization: YOUR_API_KEY'
  ```

  ```bash cURL Attach theme={null}
  curl --request POST \
    --url 'https://api.scanova.io/web-tracking/sites/7/qrs/' \
    --header 'Authorization: YOUR_API_KEY' \
    --header 'Content-Type: application/json' \
    --data '{"dynamic_url_object": 501}'
  ```
</RequestExample>

<ResponseExample>
  ```json 201 theme={null}
  {
    "id": 2,
    "site": {
      "id": 7,
      "site_id": "aZ3kP9...64-char-random-id",
      "name": "Marketing site",
      "is_active": true,
      "verified_on": "2026-09-05T09:00:00+05:30",
      "is_verified": true,
      "created": "2026-09-01T10:00:00+05:30",
      "modified": "2026-09-09T08:10:00+05:30"
    },
    "dynamic_url_object": 501,
    "is_active": true,
    "created": "2026-09-09T08:15:00+05:30",
    "modified": "2026-09-09T08:15:00+05:30"
  }
  ```
</ResponseExample>

Before attaching, use [Check attachment](/api-reference/management-api/web-tracking/check-attachment) to avoid a redundant `400`.

## Related

* [Check attachment](/api-reference/management-api/web-tracking/check-attachment)
* [Retrieve / update / detach a QR](/api-reference/management-api/web-tracking/qr-retrieve)
* [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 GET /web-tracking/sites/{site_id}/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:
  /web-tracking/sites/{site_id}/qrs/:
    get:
      summary: List attached QR codes
      operationId: listTrackingSiteQrs
      parameters:
        - name: site_id
          in: path
          required: true
          schema:
            type: integer
      responses:
        '200':
          description: QR attachments for this site.
          content:
            application/json:
              example:
                - id: 2
                  site:
                    id: 7
                    site_id: aZ3kP9...64-char-random-id
                    name: Marketing site
                    is_active: true
                    verified_on: '2026-09-05T09:00:00+05:30'
                    is_verified: true
                    created: '2026-09-01T10:00:00+05:30'
                    modified: '2026-09-09T08:10:00+05:30'
                  dynamic_url_object: 501
                  is_active: true
                  created: '2026-09-09T08:15:00+05:30'
                  modified: '2026-09-09T08:15:00+05:30'
        '404':
          description: No site with this id owned by this account.
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.

````