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

# 更新名片模板

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

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

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

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

同时支持 `PUT` 和 `PATCH`，二者接受[创建名片模板](/zh/api-reference/management-api/qr-assets/business-card-create)中记录的相同字段，包括 `template_id`（与 QR 码设计模板不同，此值在创建后可以更改）。

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

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": 8,
    "template_id": "bct-blue-01",
    "name": "Blue Card v2",
    "info": "John Doe\nCEO",
    "color": "{\"primary\":\"#0033ff\"}",
    "font": "Roboto",
    "background_img": "https://cdn.scanova.io/upload/bct/8.png"
  }
  ```
</ResponseExample>

如果 `pk` 不是该账户拥有的模板，则返回 `404`。

## 相关内容

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


## OpenAPI

````yaml api-reference/openapi/management-api.json PATCH /qr-assets/business-card-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/business-card-template/{pk}/:
    patch:
      summary: Update a business card template
      description: Both PUT and PATCH are supported.
      operationId: updateBusinessCardTemplate
      parameters:
        - name: pk
          in: path
          required: true
          schema:
            type: integer
      requestBody:
        content:
          application/json:
            example:
              name: Blue Card v2
      responses:
        '200':
          description: Template updated.
          content:
            application/json:
              example:
                id: 8
                template_id: bct-blue-01
                name: Blue Card v2
                info: John Doe\nCEO
                color: '{"primary":"#0033ff"}'
                font: Roboto
                background_img: https://cdn.scanova.io/upload/bct/8.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.

````