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

# 上传 SSL 证书

> POST /custom-domain/{pk}/ssl-certificate/

在 **Management API** 主机（`api.scanova.io`）上为域名上传已签发的 SSL 证书并将其激活，使用您的原始 Management API 密钥进行身份验证。

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

<Warning>
  仅限企业版。需要 `CUSTOM_DOMAIN_CUSTOM_SSL` 配额，该配额需人工授予——没有任何自助套餐包含此配额。需要事先存在 CSR——参见[创建 SSL 证书请求](/zh/api-reference/management-api/custom-domain/certificate-request-create)。
</Warning>

<ParamField path="pk" type="integer" required>
  域名的 `id`。
</ParamField>

<ParamField body="certificate" type="string" required>
  已签发的证书，PEM 编码。
</ParamField>

<ParamField body="certificate_chain" type="string">
  证书颁发机构的中间证书链，PEM 编码，如果您的 CA 单独提供该链。
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://api.scanova.io/custom-domain/42/ssl-certificate/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -H "Content-Type: application/json" \
    -d '{
      "certificate": "-----BEGIN CERTIFICATE-----\nMIID...\n-----END CERTIFICATE-----",
      "certificate_chain": "-----BEGIN CERTIFICATE-----\nMIID...\n-----END CERTIFICATE-----"
    }'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "detail": "Certificate activated.",
    "status": "ISSUED",
    "expires_at": "2026-12-08T00:00:00Z"
  }
  ```
</ResponseExample>

Scanova 会根据域名和 CSR 的密钥验证该证书，将其导入 AWS ACM，并将其关联以服务实际流量——此过程完全自动化，没有人工审核步骤。可能出现三种结果：

* **`200`**——已验证、导入并激活。该域名上的流量现在由新证书提供服务。
* **`202`**——已导入 ACM，但尚未签发；尚未关联以服务流量。请稍后再查看。
* **`207` Multi-Status**——已签发，但关联以服务流量失败；Scanova 支持团队已自动收到通知，将进行跟进。

如果该域名尚不存在 CSR、证书与域名或 CSR 的密钥不匹配，或 AWS ACM 拒绝导入（错误消息包含在响应中），则返回 `400`。

## 相关内容

* [获取 SSL 证书状态](/zh/api-reference/management-api/custom-domain/ssl-certificate-retrieve)——上传后检查状态。
* [创建 SSL 证书请求](/zh/api-reference/management-api/custom-domain/certificate-request-create)——上传前所需的 CSR。
* [Management API 概览](/zh/api-reference/management-api/overview)——适用于此端点的身份验证方案和配额规则。


## OpenAPI

````yaml api-reference/openapi/management-api.json POST /custom-domain/{pk}/ssl-certificate/
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}/ssl-certificate/:
    post:
      summary: Upload an SSL certificate
      description: >-
        Requires a prior CSR (see Create an SSL certificate request). Validates
        the certificate against the domain and the CSR's key, imports it into
        AWS ACM, and links it for serving traffic. A `202` means ACM accepted
        the import but hasn't finished issuing; a `207` means activation partly
        failed and support was notified automatically.
      operationId: uploadSslCertificate
      parameters:
        - name: pk
          in: path
          required: true
          schema:
            type: integer
      requestBody:
        content:
          application/json:
            example:
              certificate: '-----BEGIN CERTIFICATE-----\nMIID...\n-----END CERTIFICATE-----'
              certificate_chain: '-----BEGIN CERTIFICATE-----\nMIID...\n-----END CERTIFICATE-----'
      responses:
        '200':
          description: Certificate validated, imported, and activated for serving traffic.
          content:
            application/json:
              example:
                detail: Certificate activated.
                status: ISSUED
                expires_at: '2026-12-08T00:00:00Z'
        '202':
          description: >-
            Certificate imported into ACM but not yet issued; not linked to
            serve traffic yet.
          content:
            application/json:
              example:
                detail: Certificate imported but not yet issued. Check back shortly.
        '207':
          description: >-
            Certificate issued but linking it to serve traffic failed; support
            has been notified automatically.
          content:
            application/json:
              example:
                detail: >-
                  Certificate issued, but activation needs manual follow-up. Our
                  team has been notified.
        '400':
          description: >-
            No CSR exists for this domain yet, the certificate doesn't match the
            domain/CSR key, or AWS ACM rejected the import (error message
            included).
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.

````