> ## Documentation Index
> Fetch the complete documentation index at: https://docs.listenlabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete Response

> Request permanent deletion of a response and receive a deletion receipt

Pass both the `studyId` and `responseId` UUIDs from [Search Responses](/api-v2/search-responses). Deletion runs asynchronously and removes respondent media and response-owned data.

The receipt contains `deletionId`, `responseId`, and `status`. A `202` means the deletion is `queued` or `running`; a `200` means an existing deletion is `completed` or `failed`. Repeating the request returns the same deletion ID and current status, including after the response is removed. Use [Get Response Deletion Status](/api-v2/get-response-deletion-status) to follow progress.


## OpenAPI

````yaml api-v2/openapi.yaml DELETE /api/public/v1/responses
openapi: 3.0.3
info:
  title: Listen Labs Public API v2
  version: 2.0.0
  description: >-
    Create and launch studies, and retrieve response data programmatically.
    Authenticated with an `x-api-key` header; the key is scoped to a single
    organization.


    This spec is generated from the zod schemas in app/api/public/v1/_schema.ts
    (the ground truth for the contract) via `pnpm run generate-openapi`.
    Cross-field rules that JSON Schema cannot express (screening placement,
    min/maxSelect coupling, unique externalIds, reference resolution,
    exclusiveOption placement) are described on the relevant schemas and
    enforced by the server (returned as 400 responses).


    All error responses share one JSON envelope: `error` (human-readable
    message, may change) and `code` (stable machine-readable identifier; branch
    on this). 400 responses may also carry `issues` with per-field schema
    violations. The possible codes for each response are listed in its
    description.
servers:
  - url: https://listenlabs.ai
    description: Production
security:
  - ApiKeyAuth: []
paths:
  /api/public/v1/responses:
    delete:
      summary: Permanently delete a response's data
      description: >-
        Asynchronously removes respondent media and response-owned data.
        Repeated requests return the same deletion ID and current status,
        including after the response is removed.
      operationId: deleteResponse
      parameters:
        - name: studyId
          in: query
          required: true
          schema:
            type: string
            format: uuid
        - name: responseId
          in: query
          required: true
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: Existing deletion completed or failed.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DeleteResponseResponse'
              example:
                deletionId: de57d161-71a5-4e65-96e3-64b960a18ed2
                responseId: 877e4c64-6804-4bcb-a3d8-99805068f643
                status: completed
        '202':
          description: Deletion queued or running.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DeleteResponseResponse'
              example:
                deletionId: de57d161-71a5-4e65-96e3-64b960a18ed2
                responseId: 877e4c64-6804-4bcb-a3d8-99805068f643
                status: queued
        '400':
          description: >-
            Missing or invalid studyId or responseId query parameter. Codes:
            `bad_request`.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              examples:
                invalidIds:
                  value:
                    error: studyId and responseId must be UUIDs
                    code: bad_request
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          description: >-
            Study or response not found in the API key's organization. Codes:
            `not_found`.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              examples:
                notFound:
                  value:
                    error: Response not found
                    code: not_found
        '500':
          $ref: '#/components/responses/ServerError'
components:
  schemas:
    DeleteResponseResponse:
      type: object
      properties:
        deletionId:
          type: string
          format: uuid
        responseId:
          type: string
          format: uuid
        status:
          type: string
          enum:
            - queued
            - running
            - completed
            - failed
      required:
        - deletionId
        - responseId
        - status
      additionalProperties: false
    Error:
      type: object
      properties:
        error:
          type: string
          description: Human-readable description of the failure.
        code:
          type: string
          enum:
            - invalid_json
            - invalid_request_body
            - invalid_study_guide
            - wallet_required
            - insufficient_credits
            - bad_request
            - missing_api_key
            - invalid_api_key
            - unauthorized
            - launch_permission_denied
            - wallet_access_denied
            - forbidden
            - study_not_found
            - response_not_found
            - not_found
            - study_busy
            - concurrent_modification
            - conflict
            - internal_error
          description: >-
            Stable machine-readable error code. Branch on this, not on the
            `error` text, which may change.
      required:
        - error
        - code
      additionalProperties: false
  responses:
    Unauthorized:
      description: 'Missing or invalid API key. Codes: `missing_api_key`, `invalid_api_key`.'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          examples:
            missingApiKey:
              value:
                error: Missing x-api-key header
                code: missing_api_key
            invalidApiKey:
              value:
                error: Invalid API key
                code: invalid_api_key
    Forbidden:
      description: 'Key''s user not permitted for this resource. Codes: `forbidden`.'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          examples:
            forbidden:
              value:
                error: API key user is not a member of the key's organization
                code: forbidden
    ServerError:
      description: >-
        Internal error (details are logged server-side, not returned). Codes:
        `internal_error`.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          examples:
            internalError:
              value:
                error: Internal server error
                code: internal_error
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key

````