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

# Root-Seiten-Vorlagen für benutzerdefinierte Domains auflisten

> GET /custom-domain/templates/

Listet die Vorlagen des Kontos auf, die für die Root-Seite einer benutzerdefinierten Domain verwendet werden können, auf dem **Management-API**-Host (`api.scanova.io`), authentifiziert mit Ihrem rohen Management-API-Schlüssel.

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

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

<ResponseExample>
  ```json 200 theme={null}
  {
    "count": 1,
    "next": null,
    "previous": null,
    "results": [
      {
        "id": 3,
        "template_id": "tpl-001",
        "template_name": "Coming Soon",
        "template_description": "A simple coming-soon landing page."
      }
    ]
  }
  ```
</ResponseExample>

Die `id` einer Vorlage ist der Wert, den Sie dem Feld `template` einer Domain zuweisen, wenn deren `root_action` auf `custom_page` steht — siehe [Benutzerdefinierte Domain aktualisieren](/de/api-reference/management-api/custom-domain/update).

## Verwandte Themen

* [Benutzerdefinierte Domain aktualisieren](/de/api-reference/management-api/custom-domain/update) — eine Vorlage als Root-Seite der Domain zuweisen.
* [Übersicht über die Management API](/de/api-reference/management-api/overview) — das Authentifizierungsschema und die Quota-Regeln für diesen Endpunkt.


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /custom-domain/templates/
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/templates/:
    get:
      summary: List custom domain root-page templates
      description: >-
        Templates usable as a domain's `template` when `root_action` is
        `custom_page`.
      operationId: listCustomDomainTemplates
      responses:
        '200':
          description: Paginated list of templates.
          content:
            application/json:
              example:
                count: 1
                next: null
                previous: null
                results:
                  - id: 3
                    template_id: tpl-001
                    template_name: Coming Soon
                    template_description: A simple coming-soon landing page.
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.

````