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

# 取消共享用户对标签的关联

> DELETE /tag/attached/

在 **Management API** 主机（`api.scanova.io`）上移除某共享用户对某标签的归属关系，使用您的原始 Management API 密钥进行身份验证。

```
DELETE https://api.scanova.io/tag/attached/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField query="added_by" type="string" required>
  共享用户的电子邮件地址。必须属于该账户下已存在的共享用户。
</ParamField>

<ParamField query="tag" type="string" required>
  要取消关联的标签名称。`DELETE` 时必填（对应的 `GET` 则为可选）。
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X DELETE "https://api.scanova.io/tag/attached/?added_by=teammate@example.com&tag=vip" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
  ```
</RequestExample>

调用成功会返回 `204 No Content`。

## 此操作实际执行的内容

此操作**不会**删除该标签，也**不会**将该标签从任何二维码上移除。它只会清除*归属关系*——即哪个共享用户因添加该标签而被记为归属人——针对每一条匹配的 `TagRelation` 记录。二维码仍保留该标签；只是不再显示为该团队成员"添加"。

如果 `added_by` 不是该账户下的共享用户，或没有找到匹配的标签关联记录可清除，则返回 `400`（`{"error": ["Tag does not exist."]}`）。

## 相关内容

* [列出共享用户附加的标签](/zh/api-reference/management-api/tags/attached-list)——查找要取消关联的内容。
* [共享用户管理](/zh/api-reference/management-api/shared-users/list)——查找 `added_by` 的电子邮件地址。
* [Management API 概览](/zh/api-reference/management-api/overview)——适用于此端点的身份验证方案和配额规则。


## OpenAPI

````yaml api-reference/openapi/management-api.json DELETE /tag/attached/
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/attached/:
    delete:
      summary: Detach a tag from a shared user
      description: >-
        Clears `added_by` on every `TagRelation` row matching this shared user +
        tag name (the relation rows themselves aren't deleted, only the
        attribution) — QR codes keep the tag, it's just no longer attributed to
        that shared user. Both `added_by` and `tag` are required for DELETE.
      operationId: detachManagedTag
      parameters:
        - name: added_by
          in: query
          required: true
          schema:
            type: string
            format: email
        - name: tag
          in: query
          required: true
          schema:
            type: string
      responses:
        '204':
          description: Tag detached.
        '400':
          description: >-
            `added_by`/`tag` missing, not a shared user, or no matching tag
            relation found.
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.

````