> ## 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 QR categories

> GET /qr/category/

The QR category catalogue — the source of the `category` primary keys and slugs that every create, update, and filter call in this module needs.

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

<Warning>
  On the Management API host this endpoint **requires authentication**. The same catalogue is open on the public API host, so code ported from there will start returning `401` here unless it sends the `Authorization` header.
</Warning>

### Query parameters

<ParamField query="allowed_qr_types" type="string">
  Comma-separated filter on the QR types a category supports, e.g. `st,dy,bt`. Returns only categories that allow at least one of them.
</ParamField>

<ParamField query="view_type" type="string">
  Reshape the response into named sections instead of one `All` bucket. One of `recommended`, `use_case`, `content_type`, or `favourite`.
</ParamField>

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

<ResponseExample>
  ```json 200 OK theme={null}
  {
    "All": [
      {
        "id": 3,
        "name": "Website URL",
        "slug": "url",
        "allowed_qr_types": "dy",
        "allowed_qr_types_display": "Dynamic",
        "has_landing_page": false,
        "is_active": true,
        "is_new": false
      }
    ]
  }
  ```
</ResponseExample>

With `?view_type=recommended` the same rows come back grouped under section names instead:

```json theme={null}
{
  "Recommended QR Code Categories": [ ... ],
  "Other QR Code Categories": [ ... ]
}
```

<Note>
  The response is a **dict keyed by section name**, not a bare array, and it is never paginated. Each row also carries `description`, `preview_image`, `tags`, `helpdesk_link`, `qr_name_pattern`, `created`, and `modified`.

  `allowed_qr_types` is what makes a create call succeed or fail: a static-only category rejects `qr_type: "dy"` and vice versa. `qr_name_pattern` is the template used to auto-name a QR Code created without a `name`.
</Note>

## Related

* [Create a QR Code](/api-reference/management-api/qr/create) — where these `category` ids are used.
* [Validate QR Code content](/api-reference/management-api/qr/validate-info) — check an `info` payload against a category's schema.
* [List and add favourite categories](/api-reference/management-api/qr/favorite-category-list-create) — populate the `favourite` view.
* [Change a QR Code's category](/api-reference/management-api/qr/change-category) — move an existing Dynamic QR Code to another category.
* [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/category/
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/category/:
    get:
      summary: List QR categories
      description: >-
        The QR category catalogue — the `category` primary keys and slugs every
        create/update call needs. On the Management API host this endpoint
        REQUIRES authentication, unlike the public API where the same catalogue
        is open. Not paginated; the response is a dict keyed by section name.
      operationId: listQrCategories
      parameters:
        - name: allowed_qr_types
          in: query
          required: false
          schema:
            type: string
          description: Comma-separated filter on supported QR types, e.g. `st,dy,bt`.
        - name: view_type
          in: query
          required: false
          schema:
            type: string
            enum:
              - recommended
              - use_case
              - content_type
              - favourite
          description: >-
            Reshape the response into named sections: `recommended`, `use_case`,
            `content_type`, or `favourite`.
      responses:
        '200':
          description: Categories, keyed by section name.
          content:
            application/json:
              example:
                All:
                  - id: 3
                    name: Website URL
                    slug: url
                    allowed_qr_types: dy
                    allowed_qr_types_display: Dynamic
                    has_landing_page: false
                    is_active: true
                    is_new: false
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.

````