> ## 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 /qr/

在 **Management API** 主机（`management.scanova.io`）上列出或创建二维码，使用您的原始 Management API 密钥进行身份验证——如果您还没有设置好密钥，请参见[概览](/zh/api-reference/management-api/overview)。

```
GET  https://management.scanova.io/qr/
POST https://management.scanova.io/qr/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

`POST /qr/` 使用与常规仪表盘创建二维码端点相同的序列化器和字段约定来创建一个新的二维码。这里不重新罗列完整的字段参考，请参见 [创建二维码](/v1/api-reference/endpoint/qr_manager/create) 获取完整的必填/可选字段表（`category`、`info`、`name`、`qr_type`，以及 `pattern_info`、`custom_domain`、`expire_on`、`lead_list` 等高级字段和地理围栏选项）——那里文档记录的每个字段在此处都同样适用。

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://management.scanova.io/qr/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -H "Content-Type: application/json" \
    -d '{
      "category": 1,
      "info": "{\"type\":\"url\",\"data\":{\"url\":\"https://example.com\"}}",
      "qr_type": "dy",
      "name": "Product launch flyer"
    }'
  ```
</RequestExample>

创建成功会返回 `201 Created`，其中包含新创建的二维码，以**完整**的详情数据结构进行序列化（与 [`GET /qrcode/{qrid}/`](/zh/api-reference/management-api/qr/retrieve) 返回的结构相同）——比上方展示的精简列表结构更丰富，包含列表端点出于性能考虑而省略的 `info`、`pattern_info` 等字段。

创建二维码与从仪表盘创建二维码一样，受到相同的、基于套餐的二维码数量限制（动态/静态）的约束，此外还要通过[概览](/zh/api-reference/management-api/overview#plan-quota)中所述的 `MANAGEMENT_API`（或 `INTEGRATION_ZAPIER`/`INTEGRATION_MCP`）配额门槛。

## 相关内容

* [列出二维码](/zh/api-reference/management-api/qr/list) — 同一端点的另一个操作。
* [获取](/zh/api-reference/management-api/qr/retrieve) —— 对此列表中返回的单个二维码进行操作。
* [更新](/zh/api-reference/management-api/qr/update) —— 对此列表中返回的单个二维码进行操作。
* [删除](/zh/api-reference/management-api/qr/delete) —— 对此列表中返回的单个二维码进行操作。
* [下载二维码图片](/zh/api-reference/management-api/qr/download) —— 将这些二维码之一渲染为 PNG/SVG/PDF 等格式。
* [列出回收站中的二维码](/zh/api-reference/management-api/qr/trash) —— 从此列表中删除后二维码会去往何处。
* [Management API 概览](/zh/api-reference/management-api/overview) —— 适用于本端点的身份验证方案与配额规则。


## OpenAPI

````yaml api-reference/openapi/management-api.json POST /qr/
openapi: 3.1.0
info:
  title: Scanova Management API (v2)
  description: >-
    The complete Scanova Management API — every endpoint available at
    management.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://management.scanova.io
    description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
  - apiKeyAuth: []
paths:
  /qr/:
    post:
      summary: Create a QR code
      operationId: createManagedQrCode
      responses:
        '201':
          description: QR code created
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. management.scanova.io) — the same key sent to
        the regular API host will not authenticate.

````