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

# Supprimer un domaine personnalisé

> DELETE /custom-domain/{pk}/

Déconnecte un domaine personnalisé du compte, sur l'hôte de l'**API de gestion** (`api.scanova.io`), authentifié avec votre clé d'API de gestion brute.

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

<Note>
  Nécessite la permission `CUSTOM_DOMAIN_CAN_DELETE`.
</Note>

<ParamField path="pk" type="integer" required>
  Le `id` du domaine.
</ParamField>

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

Un appel réussi renvoie `204 No Content`.

## Les codes QR doivent d'abord être dissociés

Si le domaine est encore lié à un ou plusieurs codes QR — y compris ceux dans la corbeille —, cela renvoie `400` avec `{"error": ["This domain is linked to QR Code(s)... Delete permanently the QR Code(s) first..."]}` au lieu de le supprimer. Supprimez d'abord définitivement (pas seulement dans la corbeille) les codes QR liés avant de réessayer. `404` si `pk` n'est pas un domaine appartenant à ce compte.

## Voir aussi

* [Récupérer un domaine personnalisé](/fr/api-reference/management-api/custom-domain/retrieve) — vérifier les codes QR liés avant de supprimer.
* [Lister les domaines personnalisés](/fr/api-reference/management-api/custom-domain/list) — voir ce qui est encore connecté.
* [Présentation de l'API de gestion](/fr/api-reference/management-api/overview) — le schéma d'authentification et les règles de quota applicables à cet endpoint.


## OpenAPI

````yaml api-reference/openapi/management-api.json DELETE /custom-domain/{pk}/
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}/:
    delete:
      summary: Remove a custom domain
      description: Requires the CUSTOM_DOMAIN_CAN_DELETE permission.
      operationId: deleteCustomDomain
      parameters:
        - name: pk
          in: path
          required: true
          schema:
            type: integer
      responses:
        '204':
          description: Domain removed.
        '400':
          description: >-
            The domain is still linked to one or more QR codes (including
            trashed ones) — delete those QR codes permanently first.
        '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.

````