> ## 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 /tag/custom/

在 **Management API** 主机（`api.scanova.io`）上为请求账户创建自定义标签，使用您的原始 Management API 密钥进行身份验证。

```
POST https://api.scanova.io/tag/custom/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField body="tag" type="string" required>
  标签名称，最多 50 个字符。若包含 `<` 或 `>` 将被拒绝（用于阻止例如 `<script>` 之类的载荷）。
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://api.scanova.io/tag/custom/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -H "Content-Type: application/json" \
    -d '{ "tag": "vip" }'
  ```
</RequestExample>

<ResponseExample>
  ```json 201 theme={null}
  { "tag": "vip" }
  ```
</ResponseExample>

## 标签按名称共享，但归属不共享

底层的标签名称（`vip`）在整个系统中是共享/全局的值——创建自定义标签要么复用已有的同名标签，要么创建一个新标签。按账户区分的是*归属*记录：如果**该账户**已经拥有同名的自定义标签，此调用会返回 `400`，即使该标签名称已在其他地方使用（例如已附加到另一个账户的二维码上）。

## 相关内容

* [列出您的自定义标签](/zh/api-reference/management-api/tags/custom-list)——查看此调用添加的内容。
* [列出标签](/zh/api-reference/management-api/tags/manage)——账户完整的标签目录。
* [Management API 概览](/zh/api-reference/management-api/overview)——适用于此端点的身份验证方案和配额规则。


## OpenAPI

````yaml api-reference/openapi/management-api.json POST /tag/custom/
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:
  /tag/custom/:
    post:
      summary: Create a custom tag
      description: >-
        Creates a new custom tag (or 400s if one with this name already exists
        for the account). The underlying `Tag` row is shared/global by name —
        creating a custom tag either reuses an existing global `Tag` or creates
        one — but the `CustomTag` ownership row is per-account.
      operationId: createManagedCustomTag
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                tag:
                  type: string
                  maxLength: 50
                  description: Tag name. Rejected if it contains `<` or `>`.
              required:
                - tag
            example:
              tag: vip
      responses:
        '201':
          description: Custom tag created.
          content:
            application/json:
              example:
                tag: vip
        '400':
          description: >-
            Invalid tag name, or a custom tag with this name already exists for
            the 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.

````