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

# 验证批量操作文件

> POST /bulk-operation/validate/

在 **Management API** 主机（`api.scanova.io`）上对上传的表格进行试运行验证，对照分类的模式进行检查，使用您的原始 Management API 密钥进行身份验证。

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

<ParamField body="file" type="file" required>
  待验证的表格（CSV 或 XLSX），通常是[示例文件](/zh/api-reference/management-api/bulk-operation/sample-file)的填写副本。
</ParamField>

<ParamField body="category" type="string" required>
  该表格所对应的 QR 分类 slug，最多 100 个字符。
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://api.scanova.io/bulk-operation/validate/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -F "category=vcard" \
    -F "file=@vcard-batch.csv"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "is_valid": true,
    "validation_errors": [],
    "validation_warnings": [],
    "file_info": { "rows": 500, "columns": ["qr code id", "name", "phone"] },
    "message": "File is valid."
  }
  ```
</ResponseExample>

此调用不会创建任何内容——不会创建 `BulkOperation` 记录，也不会创建 QR 码。可用它在调用[批量生成 QR 码](/zh/api-reference/management-api/bulk-operation/generate)之前预先发现列/行错误。成功时返回 `200` 且 `is_valid: true`；否则返回 `400`，`is_valid: false` 并附带填充的 `validation_errors`。

## 相关内容

* [下载示例文件](/zh/api-reference/management-api/bulk-operation/sample-file)——此表格应据以填写的模板。
* [批量生成 QR 码](/zh/api-reference/management-api/bulk-operation/generate)——验证通过后的实际执行。
* [Management API 概览](/zh/api-reference/management-api/overview)——适用于此端点的身份验证方案和配额规则。


## OpenAPI

````yaml api-reference/openapi/management-api.json POST /bulk-operation/validate/
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/validate/:
    post:
      summary: Validate a bulk operation file
      description: >-
        A dry run: checks the uploaded sheet's columns and row data against the
        category's schema without creating a BulkOperation record or QR codes.
        Use this before `generate` to surface errors up front.
      operationId: validateBulkOperationFile
      requestBody:
        content:
          multipart/form-data:
            example:
              file: (binary file)
              category: vcard
      responses:
        '200':
          description: File is valid.
          content:
            application/json:
              example:
                is_valid: true
                validation_errors: []
                validation_warnings: []
                file_info:
                  rows: 500
                  columns:
                    - qr code id
                    - name
                    - phone
                message: File is valid.
        '400':
          description: File is invalid — see validation_errors.
          content:
            application/json:
              example:
                is_valid: false
                validation_errors:
                  - 'Row 12: missing required field ''name''.'
                validation_warnings: []
                file_info:
                  rows: 500
                  columns:
                    - qr code id
                    - name
                    - phone
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.

````