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

# Retrieve a QR Code design template

> GET /qr-assets/template/{pk}/

Retrieves one QR Code design template, on the **Management API** host (`api.scanova.io`), authenticated with your raw Management API key.

```
GET https://api.scanova.io/qr-assets/template/{pk}/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField path="pk" type="integer" required>
  The template's `id`, from [List QR Code design templates](/api-reference/management-api/qr-assets/template-list).
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl "https://api.scanova.io/qr-assets/template/12/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": 12,
    "name": "Summer Poster",
    "template_id": "a1b2c3d4e5f6",
    "template_type": "P",
    "template_type_display": "Poster",
    "pattern_info": "{\"dotStyle\":\"round\"}",
    "image": "https://cdn.scanova.io/upload/images/42/template-foo.png"
  }
  ```
</ResponseExample>

`404` if `pk` isn't a template owned by this account.

## Related

* [List QR Code design templates](/api-reference/management-api/qr-assets/template-list) — find the `id`.
* [Update a QR Code design template](/api-reference/management-api/qr-assets/template-update) — edit this template.
* [Delete a QR Code design template](/api-reference/management-api/qr-assets/template-delete) — remove this template.
* [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-assets/template/{pk}/
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-assets/template/{pk}/:
    get:
      summary: Retrieve a QR code design template
      operationId: getQrCodeTemplate
      parameters:
        - name: pk
          in: path
          required: true
          schema:
            type: integer
      responses:
        '200':
          description: One template.
          content:
            application/json:
              example:
                id: 12
                name: Summer Poster
                template_id: a1b2c3d4e5f6
                template_type: P
                template_type_display: Poster
                pattern_info: '{"dotStyle":"round"}'
                image: https://cdn.scanova.io/upload/images/42/template-foo.png
        '404':
          description: No template with this id 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.

````