> ## 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 tag details

> GET /qr/tags/details/

The account's tags with a usage count each — the data behind a tag-management screen.

```
GET    https://api.scanova.io/qr/tags/details/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField query="search" type="string">
  Substring match on the tag name.
</ParamField>

<ParamField query="ordering" type="string">
  One of `name`, `created`, `qr_code_assigned`. Prefix with `-` to sort descending, e.g. `ordering=-qr_code_assigned` for the most-used tags first.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -G "https://api.scanova.io/qr/tags/details/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -d ordering=-qr_code_assigned
  ```
</RequestExample>

<Note>
  `qr_code_assigned` is an annotated count of the QR Codes the tag is attached to, computed per request. Names are returned lowercased.
</Note>

## Related

* [List tag names](/api-reference/management-api/qr/tags-list) — the same tags as bare strings, for autocomplete.
* [Apply tags to many QR Codes](/api-reference/management-api/qr/tags-multi-create) — raise these counts in bulk.
* [Detach tags](/api-reference/management-api/qr/tag-association-delete) — drop these counts back to zero for a tag.
* [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 GET /qr/tags/details/
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/tags/details/:
    get:
      summary: List tag details
      description: >-
        The account's tags with an annotated `qr_code_assigned` count, for
        tag-management screens. Searchable on `name`; orderable by `name`,
        `created`, or `qr_code_assigned`.
      operationId: listQrTagDetails
      parameters:
        - name: search
          in: query
          required: false
          schema:
            type: string
          description: Substring match on the tag name.
        - name: ordering
          in: query
          required: false
          schema:
            type: string
          description: >-
            One of `name`, `created`, `qr_code_assigned`. Prefix with `-` to
            sort descending.
        - name: page
          in: query
          required: false
          schema:
            type: integer
            default: 1
          description: Page number.
        - name: page_size
          in: query
          required: false
          schema:
            type: integer
            default: 10
          description: Results per page, maximum `100`.
      responses:
        '200':
          description: Paginated tags with usage counts.
          content:
            application/json:
              example:
                count: 2
                next: null
                previous: null
                results:
                  - name: campaign-2026
                    qr_code_assigned: 42
                  - name: print
                    qr_code_assigned: 7
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.

````