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

# Remove an API key from listings

> Remove an already-revoked or expired key from the list-keys response. The record is retained; this call only hides it from listings.

The key must already be revoked or expired — this call does not disable an active key. The caller must own the key or hold `apiKey.write` on the current organization.




## OpenAPI

````yaml /api-reference/openapi-bundled.yaml delete /v2/api-keys/{id}/permanent
openapi: 3.0.3
info:
  title: LILT API
  description: >
    LILT API Support: https://lilt.atlassian.net/servicedesk/customer/portals


    The LILT API enables programmatic access to the full-range of LILT backend
    services including:
      * Training of and translating with interactive, adaptive machine translation
      * Large-scale translation memory
      * The Lexicon (a large-scale termbase)
      * Programmatic control of the LILT CAT environment
      * Translation memory synchronization


    Requests and responses are in JSON format. The REST API only responds to
    HTTPS / SSL requests.


    The base url for this REST API is `https://api.lilt.com/`.


    ## Authentication


    Requests are authenticated via API key, which requires the Business plan.


    Requests are authenticated using [HTTP Basic
    Auth](https://en.wikipedia.org/wiki/Basic_access_authentication). Add your
    API key as both the `username` and `password`.


    For development, you may also pass the API key via the `key` query
    parameter. This is less secure than HTTP Basic Auth, and is not recommended
    for production use.


    ## Quotas


    Our services have a general quota of 4000 requests per minute. Should you
    hit the maximum requests per minute, you will need to wait 60 seconds before
    you can send another request.
  version: v3.0.3
  license:
    name: LILT Platform Terms and Conditions
    url: https://lilt.com/lilt-platform-terms-and-conditions
servers:
  - url: https://api.lilt.com
security:
  - BasicAuth: []
  - ApiKeyAuth: []
paths:
  /v2/api-keys/{id}/permanent:
    delete:
      tags:
        - API Keys
      summary: Remove an API key from listings
      description: >
        Remove an already-revoked or expired key from the list-keys response.
        The record is retained; this call only hides it from listings.


        The key must already be revoked or expired — this call does not disable
        an active key. The caller must own the key or hold `apiKey.write` on the
        current organization.
      operationId: permanentlyDeleteApiKey
      parameters:
        - name: id
          in: path
          required: true
          description: The API key's unique identifier.
          schema:
            type: string
      responses:
        '204':
          description: API key removed from listings.
        '400':
          description: >-
            The key is still active — revoke it or let it expire first — or the
            authenticated user has no active organization.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiKeyError'
        '401':
          description: The request is not authenticated.
        '403':
          description: The caller does not own the key and lacks `apiKey.write`.
        '404':
          description: API key not found, or belongs to another organization.
        default:
          description: Unexpected error.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    ApiKeyError:
      type: object
      description: >-
        Error response returned by the API Keys endpoints. The human-readable
        message is carried in the `error` field.
      properties:
        error:
          type: string
          description: A human-readable message describing the error.
          example: No active organization
    Error:
      type: object
      properties:
        message:
          type: string
          description: A human-readable message describing the error.
      description: |
        Response in the event of an unexpected error.
      example:
        message: Internal server error.
  securitySchemes:
    BasicAuth:
      type: http
      scheme: basic
    ApiKeyAuth:
      type: apiKey
      name: key
      in: query

````