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

# 列出可用于 QR 分配的已验证域名

> GET /custom-domain/verified/

在 **Management API** 主机（`api.scanova.io`）上列出可用于 QR 短链接分配的域名，使用您的原始 Management API 密钥进行身份验证。

```
GET https://api.scanova.io/custom-domain/verified/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField query="exclude_platform_domains" type="boolean">
  省略平台默认域名（`new.scnv.io`），仅保留该账户拥有的域名。
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl "https://api.scanova.io/custom-domain/verified/?exclude_platform_domains=true" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  [
    {
      "id": 0,
      "domain": "new.scnv.io",
      "is_default": true,
      "disable_slug_case": false,
      "is_platform_domain": true
    },
    {
      "id": 42,
      "domain": "links.example.com",
      "is_default": false,
      "disable_slug_case": false,
      "is_platform_domain": false
    }
  ]
  ```
</ResponseExample>

这是[列出自定义域名](/zh/api-reference/management-api/custom-domain/list)适用于选择器的对应端点：不分页，并在未传入 `exclude_platform_domains=true` 时包含一条合成的平台默认行（`id: 0`）。对于只应接受该账户自己拥有的域名的流程，请使用 `exclude_platform_domains=true`——`id: 0` 这一哨兵值并非真实的域名记录，无法通过 `/custom-domain/{pk}/` 端点解析。

## 相关内容

* [列出自定义域名](/zh/api-reference/management-api/custom-domain/list)——包含验证和 DNS 详细信息的完整分页记录集。
* [验证自定义域名的 DNS 记录](/zh/api-reference/management-api/custom-domain/verify)——让某个域名出现在此处。
* [Management API 概览](/zh/api-reference/management-api/overview)——适用于此端点的身份验证方案和配额规则。


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /custom-domain/verified/
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:
  /custom-domain/verified/:
    get:
      summary: List verified domains for QR assignment
      description: >-
        A flat (non-paginated) list of domains eligible for QR short-link
        assignment: the account's verified custom domains, plus a synthesized
        platform-default entry (`id: 0`) unless `exclude_platform_domains=true`
        is passed.
      operationId: listVerifiedCustomDomains
      parameters:
        - name: exclude_platform_domains
          in: query
          required: false
          schema:
            type: boolean
          description: >-
            Omit the platform default domain, keeping only domains this account
            owns.
      responses:
        '200':
          description: Plain array of verified domains (no pagination envelope).
          content:
            application/json:
              example:
                - id: 0
                  domain: new.scnv.io
                  is_default: true
                  disable_slug_case: false
                  is_platform_domain: true
                - id: 42
                  domain: links.example.com
                  is_default: false
                  disable_slug_case: false
                  is_platform_domain: false
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.

````