> ## 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.
# Subir un certificado SSL
> POST /custom-domain/{pk}/ssl-certificate/
Sube un certificado SSL emitido para un dominio y lo activa, en el host de la **API de gestión** (`api.scanova.io`), autenticado con su clave de API de gestión sin procesar.
```
POST https://api.scanova.io/custom-domain/{pk}/ssl-certificate/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```
Solo Enterprise. Requiere la cuota `CUSTOM_DOMAIN_CUSTOM_SSL`, que se otorga manualmente — ningún plan de autoservicio la incluye. Requiere una CSR previa — consulte [Crear una solicitud de certificado SSL](/es/api-reference/management-api/custom-domain/certificate-request-create).
El `id` del dominio.
El certificado emitido, codificado en PEM.
La cadena intermedia de la autoridad certificadora, codificada en PEM, si su CA la proporciona por separado.
```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-----"
}'
```
```json 200 theme={null}
{
"detail": "Certificate activated.",
"status": "ISSUED",
"expires_at": "2026-12-08T00:00:00Z"
}
```
Scanova valida el certificado contra el dominio y la clave de la CSR, lo importa a AWS ACM y lo vincula para servir tráfico real — esto está totalmente automatizado, sin paso de revisión manual. Son posibles tres resultados:
* **`200`** — validado, importado y activado. El tráfico de este dominio ahora se sirve con el nuevo certificado.
* **`202`** — importado a ACM pero aún no emitido; todavía no vinculado para servir tráfico. Vuelva a comprobar en breve.
* **`207` Multi-Status** — emitido, pero la vinculación para servir tráfico falló; el equipo de soporte de Scanova ha sido notificado automáticamente y dará seguimiento.
`400` si aún no existe una CSR para este dominio, el certificado no coincide con el dominio o con la clave de la CSR, o AWS ACM rechaza la importación (el mensaje de error se incluye en la respuesta).
## Relacionado
* [Obtener el estado del certificado SSL](/es/api-reference/management-api/custom-domain/ssl-certificate-retrieve) — comprobar el estado tras subirlo.
* [Crear una solicitud de certificado SSL](/es/api-reference/management-api/custom-domain/certificate-request-create) — la CSR requerida antes de subir.
* [Resumen de la API de gestión](/es/api-reference/management-api/overview) — el esquema de autenticación y las reglas de cuota aplicables a este endpoint.
## 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.
````