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

# Tag management

> GET /tag/list/

Tags are the labels attached to QR codes for filtering and reporting — the same tags shown as chips throughout the dashboard's QR Codes list. This endpoint returns the tags visible to the authenticated account, read-only.

<Note>
  Requires a Management API key with `MANAGEMENT_API` (or `MANAGEMENT_API_SANDBOX`) quota, sent as the raw `Authorization` header value. See the [Management API overview](/api-reference/management-api/overview).
</Note>

## List tags

<RequestExample>
  ```bash cURL theme={null}
  curl --request GET \
    --url 'https://management.scanova.io/tag/list/' \
    --header 'Authorization: YOUR_API_KEY'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "count": 1,
    "next": null,
    "previous": null,
    "results": [
      {
        "id": 3369,
        "name": "docs-v2-test-tag"
      }
    ]
  }
  ```
</ResponseExample>

Results are paginated (page size 10 by default, up to 100 via `page_size`).

<ParamField query="name" type="string">
  Case-insensitive prefix match — returns tags whose name starts with this value.
</ParamField>

<ParamField query="page" type="integer">
  Page number to retrieve.
</ParamField>

<ParamField query="page_size" type="integer" default="10">
  Number of tags per page. Maximum 100.
</ParamField>

### Response fields

<ResponseField name="id" type="integer">
  Tag ID.
</ResponseField>

<ResponseField name="name" type="string">
  Tag name, always returned lowercase regardless of how it was originally entered.
</ResponseField>

<Note>
  This list scopes to tags actually attached to (or assignable against) the account's own QR codes — it is not a global tag directory. If the account has [tag-based shared-user permissions](/team/roles-and-permissions) enabled, the set returned can additionally depend on which tags the authenticated account is scoped to.
</Note>

<Warning>
  There is no corresponding create/delete endpoint on the Management API — tags are created implicitly when attached to a QR code (via the dashboard, the QR create/update endpoints, or bulk operations), not through a standalone tag-management call.
</Warning>

## Related

* [Folder management](/api-reference/management-api/folders/list) — the other QR-organization mechanism, used alongside (or instead of) tags.
* [List / create QR codes](/api-reference/management-api/qr/list) — filter QR codes by tag name via `?tags=`.
* [Shared user management](/api-reference/management-api/shared-users/invite) — where a tag ID from this list is used to scope a teammate's visibility.
* [Roles & permissions](/team/roles-and-permissions) — how tag-based permission scoping works from the dashboard side.


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /tag/list/
openapi: 3.1.0
info:
  title: Scanova Management API (v2)
  description: >-
    The complete Scanova Management API — every endpoint available at
    management.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://management.scanova.io
    description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
  - apiKeyAuth: []
paths:
  /tag/list/:
    get:
      summary: List tags
      operationId: listManagedTags
      responses:
        '200':
          description: List of tags
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. management.scanova.io) — the same key sent to
        the regular API host will not authenticate.

````