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

# 通过邮件发送 DNS 设置说明

> POST /custom-domain/{pk}/send-instructions/

在 **Management API** 主机（`api.scanova.io`）上将域名的 DNS 设置说明通过邮件发送给收件人，使用您的原始 Management API 密钥进行身份验证。

```
POST https://api.scanova.io/custom-domain/{pk}/send-instructions/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField path="pk" type="integer" required>
  域名的 `id`，来自[列出自定义域名](/zh/api-reference/management-api/custom-domain/list)。
</ParamField>

<ParamField body="email" type="string" required>
  收件人邮箱地址。无需是 Scanova 用户——此端点旨在将设置工作转交给负责管理该域名 DNS 的人员（例如 IT 团队）。
</ParamField>

<ParamField body="note" type="string">
  包含在邮件中的可选备注，最多 1000 个字符。
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://api.scanova.io/custom-domain/42/send-instructions/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -H "Content-Type: application/json" \
    -d '{
      "email": "it-team@example.com",
      "note": "Please add these records before Friday."
    }'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  { "detail": "Setup instructions sent." }
  ```
</ResponseExample>

邮件中包含该域名的 CNAME 目标和 TXT 验证值——与[列出自定义域名](/zh/api-reference/management-api/custom-domain/list)返回的值相同。如果 `pk` 不是该账户拥有的域名，则返回 `404`。

## 相关内容

* [列出自定义域名](/zh/api-reference/management-api/custom-domain/list)——在 API 响应中查看相同的 DNS 值。
* [获取 Domain Connect 设置链接](/zh/api-reference/management-api/custom-domain/domain-connect-link)——注册商支持时的一键替代方案。
* [验证自定义域名的 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 POST /custom-domain/{pk}/send-instructions/
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/{pk}/send-instructions/:
    post:
      summary: Email DNS setup instructions
      description: >-
        Emails the CNAME target and TXT verification value to an arbitrary
        recipient — useful for handing setup off to a domain owner's IT team,
        who need not be a Scanova user.
      operationId: sendCustomDomainSetupInstructions
      parameters:
        - name: pk
          in: path
          required: true
          schema:
            type: integer
      requestBody:
        content:
          application/json:
            example:
              email: it-team@example.com
              note: Please add these records before Friday.
      responses:
        '200':
          description: Instructions sent.
          content:
            application/json:
              example:
                detail: Setup instructions sent.
        '404':
          description: No domain with this id owned by this 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.

````