> ## 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 名称/标签

> POST /bulk-operation/update-details/

在 **Management API** 主机（`api.scanova.io`）上根据上传的表格异步更新大量 QR 码的名称和标签，使用您的原始 Management API 密钥进行身份验证。

```
POST https://api.scanova.io/bulk-operation/update-details/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField body="name" type="string" required>
  此操作的标签，显示在[列出批量操作](/zh/api-reference/management-api/bulk-operation/list)中。
</ParamField>

<ParamField body="file" type="file" required>
  填写好的表格。必须恰好包含 `qr code id`、`name`、`tags` 这几列——参见[下载批量更新示例表格](/zh/api-reference/management-api/bulk-operation/update-sheet)（`?type=update_details`）。
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://api.scanova.io/bulk-operation/update-details/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -F "name=October tag cleanup" \
    -F "file=@tag-updates.csv"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "operation_id": "bo-upd-001",
    "message": ["Your file is being processed. We'll email you once it's ready."]
  }
  ```
</ResponseExample>

异步——轮询[列出批量操作](/zh/api-reference/management-api/bulk-operation/list)获取 `status`/`progress`。如果文件未恰好包含所需的三列，或行数据无效，则返回 `400`。如果账户缺少 `BULK_OPERATION` 配额、套餐不活跃，或缺少 `BULK_OPERATION_CAN_UPDATE` 权限，则返回 `403`。

## 相关内容

* [下载批量更新示例表格](/zh/api-reference/management-api/bulk-operation/update-sheet)——此文件的来源。
* [批量更新 QR 内容](/zh/api-reference/management-api/bulk-operation/update-content)——改为更新目标内容的对应端点。
* [列出批量操作](/zh/api-reference/management-api/bulk-operation/list)——轮询完成状态。
* [Management API 概览](/zh/api-reference/management-api/overview)——适用于此端点的身份验证方案和配额规则。


## OpenAPI

````yaml api-reference/openapi/management-api.json POST /bulk-operation/update-details/
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:
  /bulk-operation/update-details/:
    post:
      summary: Bulk-update QR name/tags
      description: >-
        Updates `name` and `tags` for many QR codes from an uploaded sheet,
        asynchronously. The sheet must have exactly the columns `qr code id`,
        `name`, `tags`.
      operationId: bulkUpdateDetails
      requestBody:
        content:
          multipart/form-data:
            example:
              name: October tag cleanup
              file: (binary file)
      responses:
        '200':
          description: Update started.
          content:
            application/json:
              example:
                operation_id: bo-upd-001
                message:
                  - >-
                    Your file is being processed. We'll email you once it's
                    ready.
        '400':
          description: >-
            File doesn't have exactly the required columns, or row data is
            invalid.
        '403':
          description: >-
            Missing BULK_OPERATION quota, inactive plan, or missing
            BULK_OPERATION_CAN_UPDATE permission.
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.

````