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

# Formularantwort löschen

> DELETE /forms/{form_id}/responses/{response_id}/

Löscht eine einzelne Formularantwort.

<Note>
  Erfordert einen Management-API-Schlüssel mit `MANAGEMENT_API`- (oder `MANAGEMENT_API_SANDBOX`-)Quota und die Berechtigung `LEAD_GENERATION_ENTRY_CAN_DELETE`, gesendet als roher `Authorization`-Header-Wert — siehe die [Übersicht über die Management API](/de/api-reference/management-api/overview).
</Note>

<ParamField path="form_id" type="string" required>
  Die `form_id` des Formulars.
</ParamField>

<ParamField path="response_id" type="string" required>
  Die `id` der Antwort, aus [Formularantworten auflisten](/de/api-reference/management-api/forms/responses-list).
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl --request DELETE \
    --url 'https://api.scanova.io/forms/F8a9b0c1d2e3f4g5h/responses/b3f1c9a2-1234-4d1a-9c6e-3a2b7f9d1e40/' \
    --header 'Authorization: YOUR_API_KEY'
  ```
</RequestExample>

Ein erfolgreicher Aufruf gibt `204 No Content` zurück. `404`, wenn `form_id` diesem Konto nicht gehört oder `response_id` keine Antwort auf dieses Formular ist.

## Verwandte Themen

* [Formularantworten auflisten](/de/api-reference/management-api/forms/responses-list) — die `id` der Antwort finden.
* [Formularantworten massenhaft löschen](/de/api-reference/management-api/forms/responses-bulk-delete) — stattdessen mehrere auf einmal löschen.
* [Übersicht über die Management API](/de/api-reference/management-api/overview) — das Authentifizierungsschema und die Quota-Architektur, zu der dieser Endpunkt gehört.


## OpenAPI

````yaml api-reference/openapi/management-api.json DELETE /forms/{form_id}/responses/{response_id}/
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:
  /forms/{form_id}/responses/{response_id}/:
    delete:
      summary: Delete a form response
      operationId: deleteManagedFormResponse
      responses:
        '204':
          description: Deleted.
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.

````