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

# Check attachment

> GET /web-tracking/sites/{site_id}/check-qr-attachment/

Checks whether a tracking site has any QR Code attached at all, or (with `qr_id`) whether one specific QR Code is attached to it — useful before calling [Attach a QR](/api-reference/management-api/web-tracking/qrs-list-create) to avoid a redundant `400` from the one-attachment-per-QR constraint.

<Note>
  Requires the account's `CONVERSION_TRACKING` quota.
</Note>

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

<ParamField query="qr_id" type="integer">
  A `dynamic_url_object` ID to check specifically. Omit to check whether the site has *any* QR Code attached.
</ParamField>

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

<ResponseExample>
  ```json 200 theme={null}
  { "is_attached": true }
  ```
</ResponseExample>

`404` if `site_id` isn't owned by this account.

## Related

* [List / attach QR Codes](/api-reference/management-api/web-tracking/qrs-list-create)
* [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}/check-qr-attachment/
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}/check-qr-attachment/:
    get:
      summary: Check QR attachment
      operationId: checkTrackingSiteQrAttachment
      parameters:
        - name: site_id
          in: path
          required: true
          schema:
            type: integer
        - name: qr_id
          in: query
          required: false
          schema:
            type: integer
          description: >-
            A dynamic_url_object id to check specifically; omit to check whether
            the site has any QR attached.
      responses:
        '200':
          description: Attachment status.
          content:
            application/json:
              example:
                is_attached: true
        '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.

````