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

# 更新 QR 码设计模板

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

在 **Management API** 主机（`api.scanova.io`）上更新账户拥有的 QR 设计模板，使用您的原始 Management API 密钥进行身份验证。

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

<ParamField path="pk" type="integer" required>
  模板的 `id`。
</ParamField>

同时支持 `PUT`（完整替换）和 `PATCH`（部分更新），二者接受与[创建 QR 码设计模板](/zh/api-reference/management-api/qr-assets/template-create)中记录相同的 `name`/`pattern_info`/`image` 字段。

<RequestExample>
  ```bash cURL theme={null}
  curl -X PATCH "https://api.scanova.io/qr-assets/template/12/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -H "Content-Type: application/json" \
    -d '{ "name": "Winter Poster" }'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": 12,
    "name": "Winter 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>

## `template_type` 无法在此更改

`template_type` 仅在创建时可设置——在 `PUT`/`PATCH` 请求体中发送该字段会被静默忽略，而不是报错，因此模板在其整个生命周期内保持原始的海报/普通类型。如果 `pk` 不是该账户拥有的模板，则返回 `404`。

## 相关内容

* [获取 QR 码设计模板](/zh/api-reference/management-api/qr-assets/template-retrieve)——更新前先查看。
* [创建 QR 码设计模板](/zh/api-reference/management-api/qr-assets/template-create)——此更新复用的字段参考。
* [删除 QR 码设计模板](/zh/api-reference/management-api/qr-assets/template-delete)——将其彻底删除。
* [Management API 概览](/zh/api-reference/management-api/overview)——适用于此端点的身份验证方案和配额规则。


## OpenAPI

````yaml api-reference/openapi/management-api.json PATCH /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}/:
    patch:
      summary: Update a QR code design template
      description: >-
        Both PUT (full replace) and PATCH (partial) are supported.
        `template_type` is create-only — sending it here is silently ignored,
        not rejected.
      operationId: updateQrCodeTemplate
      parameters:
        - name: pk
          in: path
          required: true
          schema:
            type: integer
      requestBody:
        content:
          application/json:
            example:
              name: Winter Poster
      responses:
        '200':
          description: Template updated.
          content:
            application/json:
              example:
                id: 12
                name: Winter 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.

````