> ## 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 /media/bulk/{pk}/

在**管理 API** 主机 (`api.scanova.io`) 上更新此账户拥有的批量媒体批次，使用您的原始管理 API 密钥进行身份验证。

```
PUT   https://api.scanova.io/media/bulk/{pk}/
PATCH https://api.scanova.io/media/bulk/{pk}/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField path="pk" type="integer" required>
  批次的 `id`。
</ParamField>

<ParamField body="status" type="string">
  `new`、`completed` 或 `failed`。
</ParamField>

<ParamField body="count" type="integer">
  更新后的预期文件数量 —— 更改此值会重新运行 `BULK_MEDIA` 配额检查。
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X PATCH "https://api.scanova.io/media/bulk/12/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -H "Content-Type: application/json" \
    -d '{ "status": "completed" }'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": 12,
    "operation_id": "BM-9F3K2LQP",
    "status": "completed",
    "count": 25,
    "upload_count": 25,
    "created": "2026-09-08T09:00:00Z",
    "modified": "2026-09-08T09:10:00Z"
  }
  ```
</ResponseExample>

同时支持 `PUT` 和 `PATCH`。如果更改 `count` 未通过 `BULK_MEDIA` 配额检查，则返回 `403`。如果 `pk` 不属于此账户的批次，则返回 `404`。

## 相关内容

* [获取批量媒体批次](/zh/api-reference/management-api/user-media/bulk-retrieve) —— 更新前查看。
* [删除批量媒体批次](/zh/api-reference/management-api/user-media/bulk-delete) —— 将其彻底删除。
* [管理 API 概述](/zh/api-reference/management-api/overview) —— 适用于此端点的身份验证方案和配额规则。


## OpenAPI

````yaml api-reference/openapi/management-api.json PATCH /media/bulk/{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:
  /media/bulk/{pk}/:
    patch:
      summary: Update a bulk media batch
      description: Both PUT and PATCH are supported.
      operationId: updateBulkMedia
      parameters:
        - name: pk
          in: path
          required: true
          schema:
            type: integer
      requestBody:
        content:
          application/json:
            example:
              status: completed
      responses:
        '200':
          description: Batch updated.
          content:
            application/json:
              example:
                id: 12
                operation_id: BM-9F3K2LQP
                status: completed
                count: 25
                upload_count: 25
                created: '2026-09-08T09:00:00Z'
                modified: '2026-09-08T09:00:00Z'
        '403':
          description: Quota check failed if count was changed.
        '404':
          description: No batch 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.

````