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

# Update a QR Code's tags

> PATCH /qr/{qrid}/tags/

Sets the tags on one QR Code, without going through the full update serializer.

```
PATCH  https://api.scanova.io/qr/{qrid}/tags/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField path="qrid" type="string" required>
  The QR Code's `qrid`.
</ParamField>

<ParamField body="tags" type="string">
  Write-only, comma-separated tag names. Names are lowercased, and any that don't exist yet are created.
</ParamField>

<ParamField body="tags_list" type="array">
  Read-only — the resulting tags.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X PATCH "https://api.scanova.io/qr/Qa1b2c3d4e5f6g7h8/tags/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -H "Content-Type: application/json" \
    -d '{
        "tags": "campaign-2026, print"
    }'
  ```
</RequestExample>

<Note>
  Omitting `tags` and sending it empty mean different things:

  * **`tags` absent from the body** — existing tags are preserved.
  * **`"tags": ""`** — all tags are removed from this QR Code.

  So a `PATCH` with an empty body is a no-op, not a clear.
</Note>

## Related

* [Apply tags to many QR Codes](/api-reference/management-api/qr/tags-multi-create) — the bulk equivalent.
* [List tag names](/api-reference/management-api/qr/tags-list) — the existing tag names to choose from.
* [Detach tags](/api-reference/management-api/qr/tag-association-delete) — remove a tag across the whole 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 PATCH /qr/{qrid}/tags/
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/{qrid}/tags/:
    patch:
      summary: Update a QR code's tags
      description: >-
        Sets the tags on one QR code. `tags` is a write-only comma-separated
        string and `tags_list` is the read-only result. Omitting `tags` entirely
        preserves the existing tags; sending an empty string clears them.
      operationId: updateQrCodeTags
      parameters:
        - name: qrid
          in: path
          required: true
          schema:
            type: string
          description: >-
            The QR code's `qrid` — the opaque public identifier returned by the
            list endpoint, not the numeric `id`.
      requestBody:
        content:
          application/json:
            example:
              tags: campaign-2026, print
      responses:
        '200':
          description: Tags updated.
          content:
            application/json:
              example:
                tags_list:
                  - campaign-2026
                  - print
        '404':
          description: No QR code with this `qrid` 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.

````