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

# Permanently delete entity record

> <Info>This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.</Info>

Erases one record from the entity's trash for good. It can't be restored afterwards.

Only a record already in the trash can be erased. Delete a live record with [Delete entity record](/api-reference/delete-entity-record) first. The record's earlier versions in the entity's version history aren't erased with it, and expire on the history's usual schedule.

Erasing a record triggers the app's webhooks for this entity, but not the automations or workflows that listen for deleted records.

<Note>This endpoint accepts a personal API key belonging to a user with editor access to the app. A read-only key is refused, and workspace API keys are not accepted.</Note>



## OpenAPI

````yaml /developers/references/app-management/app-management-openapi.json delete /api/apps/{app_id}/entities/{entity_name}/{entity_id}/permanent
openapi: 3.1.0
info:
  title: Base44 App Management API
  version: 1.0.0
servers:
  - url: https://app.base44.com
security:
  - PersonalAccessTokenAuth: []
paths:
  /api/apps/{app_id}/entities/{entity_name}/{entity_id}/permanent:
    delete:
      summary: Permanently delete entity record
      description: >-
        <Info>This API is in beta. Endpoints, fields, and behavior may still
        change, so avoid depending on it in production.</Info>


        Erases one record from the entity's trash for good. It can't be restored
        afterwards.


        Only a record already in the trash can be erased. Delete a live record
        with [Delete entity record](/api-reference/delete-entity-record) first.
        The record's earlier versions in the entity's version history aren't
        erased with it, and expire on the history's usual schedule.


        Erasing a record triggers the app's webhooks for this entity, but not
        the automations or workflows that listen for deleted records.


        <Note>This endpoint accepts a personal API key belonging to a user with
        editor access to the app. A read-only key is refused, and workspace API
        keys are not accepted.</Note>
      operationId: >-
        delete_entity_permanently_api_apps__app_id__entities__entity_name___entity_id__permanent_delete
      parameters:
        - name: entity_id
          in: path
          required: true
          schema:
            type: string
            description: >-
              ID of the deleted record, as `id` in the response of [List deleted
              entity records](/api-reference/list-deleted-entity-records).
            title: Entity Id
          description: >-
            ID of the deleted record, as `id` in the response of [List deleted
            entity records](/api-reference/list-deleted-entity-records).
          example: 6886b8d390dc7e2f4a2c91b3
        - name: app_id
          in: path
          required: true
          schema:
            type: string
            description: ID of the app that owns the entity.
            title: App Id
          description: ID of the app that owns the entity.
          example: 6820f3a4e7b91d003c45a1f2
        - name: entity_name
          in: path
          required: true
          schema:
            type: string
            description: >-
              Name of the entity, exactly as [List entity
              schemas](/api-reference/list-entity-schemas) reports it. Don't
              pass `User` here. It doesn't fail, but it reads and writes a
              separate, disconnected set of records stored under that name, not
              the app's real user accounts, which are managed through their own
              endpoints.
            title: Entity Name
          description: >-
            Name of the entity, exactly as [List entity
            schemas](/api-reference/list-entity-schemas) reports it. Don't pass
            `User` here. It doesn't fail, but it reads and writes a separate,
            disconnected set of records stored under that name, not the app's
            real user accounts, which are managed through their own endpoints.
          example: Invoice
      responses:
        '200':
          description: The record was erased.
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
                title: DeleteEntityRecordResponse
                description: Confirmation that a record was deleted.
                properties:
                  success:
                    type: boolean
                    title: Success
                    description: >-
                      Always `true`. A delete that doesn't happen returns an
                      error instead.
                    example: true
                required:
                  - success
        '401':
          description: Missing or invalid credentials.
        '403':
          description: >-
            You don't have editor access to this app, or your API key is
            read-only.
        '404':
          description: >-
            App not found, the app has no entity with this name, or the entity's
            trash holds no record with this ID, including when the record is
            still live.
        '429':
          description: >-
            Rate limit exceeded. The base limit is 30 requests every 30 seconds.
            See [Rate
            limits](/developers/references/apps-api/get-started/rate-limits) for
            the multiplier your plan gets.
components:
  securitySchemes:
    PersonalAccessTokenAuth:
      type: http
      scheme: bearer
      description: 'Personal access token, sent as `Authorization: Bearer <token>`.'

````