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

# Delete a record configuration

> Deletes the configuration and its records. When the set keeps history, each record first gets a delete event in its history, keeping every earlier version; this runs in the background after the reply and is resumed after a restart. The records are purged only once every event is written. The kept history stays readable by root and admin, and only `DELETE /records/config/{config_id}/history` erases it. A set without history has its records purged at once.



## OpenAPI

````yaml /api-reference/endpoint/records/openapi.json delete /records/config/{id}
openapi: 3.1.0
info:
  title: Records API
  version: 1.1.0
  description: >-
    Record configurations (schemas, views, versions) and the records that
    conform to them. Record IDs are server-generated, config IDs are
    client-supplied (`^[a-zA-Z0-9_-]+$`). Configs and records are updated with
    PUT: a config update applies only the fields sent, a record update merges
    `data`. Editing a config schema does not retroactively re-validate existing
    records. Publish a config version to snapshot the stored config; list and
    read versions to see its history.
servers:
  - url: https://api.quiva.ai
    description: Production API server
security:
  - bearerAuth: []
  - apiKeyAuth: []
tags:
  - name: Record Configs
    description: >-
      Manage record configuration schemas. Each configuration defines the
      structure (fields, types, validation rules) that records must conform to.
  - name: Records
    description: >-
      Manage individual data records. Each record belongs to exactly one
      configuration and its data is validated against that configuration's
      schema.
  - name: Record Config Collections
    description: Groups of record configs.
  - name: Record Config Versions
    description: Published snapshots of a record config.
  - name: Record History
    description: The change history of a record.
  - name: Record Assessment
  - name: Strategy and Simulation
  - name: Record Metrics
paths:
  /records/config/{id}:
    parameters:
      - name: id
        in: path
        required: true
        description: Record configuration ID
        schema:
          type: string
    delete:
      tags:
        - Record Configs
      summary: Delete a record configuration
      description: >-
        Deletes the configuration and its records. When the set keeps history,
        each record first gets a delete event in its history, keeping every
        earlier version; this runs in the background after the reply and is
        resumed after a restart. The records are purged only once every event is
        written. The kept history stays readable by root and admin, and only
        `DELETE /records/config/{config_id}/history` erases it. A set without
        history has its records purged at once.
      operationId: deleteRecordConfig
      responses:
        '200':
          description: Configuration deleted
          content:
            application/json:
              schema:
                allOf:
                  - $ref: '#/components/schemas/Response'
                  - properties:
                      body:
                        $ref: '#/components/schemas/SuccessMessage'
        '400':
          description: Missing required parameter
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Record configuration not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: The pending delete could not be recorded; nothing was deleted
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    Response:
      type: object
      properties:
        status_code:
          type: integer
          description: HTTP status code echoed in the response body.
        body:
          type: object
          description: Response payload.
    SuccessMessage:
      type: object
      properties:
        message:
          type: string
          enum:
            - success
      example:
        message: success
    ErrorResponse:
      type: object
      properties:
        status_code:
          type: integer
        body:
          type: object
          properties:
            error:
              type: string
              description: Human-readable error message.
      example:
        status_code: 400
        body:
          error: field 'rating' is required
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
    apiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.