> ## 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 and add favourite categories

> GET, POST /qr/favorite/

Lists the calling account's favourited QR categories, and adds new ones. One `ListCreateAPIView`, so both operations live on the same path.

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

Favourites are always scoped to the account the key belongs to, and the response is not paginated.

<ParamField body="qr_category" type="integer" required>
  Primary key of the category to favourite, from [List QR categories](/api-reference/management-api/qr/category-list).
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://api.scanova.io/qr/favorite/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -H "Content-Type: application/json" \
    -d '{
        "qr_category": 3
    }'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 OK theme={null}
  [
    { "id": 17, "qr_category": 3 }
  ]
  ```
</ResponseExample>

<Note>
  Favourites are what `?view_type=favourite` reads on [List QR categories](/api-reference/management-api/qr/category-list) — add one here and it shows up in that section.
</Note>

## Related

* [Remove a favourite category](/api-reference/management-api/qr/favorite-category-delete) — the delete side of this resource.
* [List QR categories](/api-reference/management-api/qr/category-list) — the categories you can favourite, and the `favourite` view that reads them.
* [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/favorite/
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/favorite/:
    get:
      summary: List favourite QR categories
      description: >-
        The signed-in account's favourited QR categories. Scoped to the caller
        and unpaginated.
      operationId: listFavoriteQrCategories
      responses:
        '200':
          description: Array of favourite-category rows.
          content:
            application/json:
              example:
                - id: 17
                  qr_category: 3
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.

````