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

# Delete Organisation Llm Key

> Remove the org's key for ``provider`` (DB row + GCP secret).



## OpenAPI

````yaml https://api.truestate.io/openapi.json delete /organisations/llm-keys/{provider}
openapi: 3.1.0
info:
  title: TrueState Backend API
  summary: >-
    TrueState is an AI platform for business users to create high-impact AI
    solutions.
  description: >

    This **[TrueState](https://www.truestate.io/)** backend API allows our
    clients to automate and more powerfully retrieve and modify data from the
    TrueState platform.


    Example use cases include:


    - Accessing embeddings for a dataset.

    - Automating the process of dataset creation and model retraining as your
    data changes.

    - Much more.


    Our backend is built using the [FastAPI](https://fastapi.tiangolo.com/)
    framework in python

    using [Auth0](https://auth0.com/) and [Client API
    Keys](https://www.truestate.io/dawn/docs) for internal an external
    authentication, respectively.

    Our backend is designed to be secure, scalable, easy to use and well
    documented _(each router with its own linked docs page)_.

    Clients can only access data from their own organisation, as setup in Auth0
    our the Client API Keys. See how
    **[here](https://www.truestate.io/dawn/docs)**.


    **PS**: You can view this API documentation in either
    **[Swagger](swagger/docs)** or **[Redoc](redoc/)**, but only the swagger
    lets you test calls.
  contact:
    name: True State Support
    url: https://www.truestate.io/dawn/docs
    email: support@truestate.io
  license:
    name: Private
    url: https://www.apache.org/licenses/LICENSE-2.0.html
  version: 0.13.95
servers: []
security: []
paths:
  /organisations/llm-keys/{provider}:
    delete:
      tags:
        - organisation-llm-keys
      summary: Delete Organisation Llm Key
      description: Remove the org's key for ``provider`` (DB row + GCP secret).
      operationId: delete_organisation_llm_key_organisations_llm_keys__provider__delete
      parameters:
        - name: provider
          in: path
          required: true
          schema:
            $ref: '#/components/schemas/LlmApiKeyProvider'
        - name: Api-key
          in: header
          required: false
          schema:
            anyOf:
              - type: string
              - type: 'null'
            title: Api-Key
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/StandardStatusReply'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
        - HTTPBearer: []
components:
  schemas:
    LlmApiKeyProvider:
      type: string
      enum:
        - openai
        - anthropic
        - google
        - xai
        - openrouter
      title: LlmApiKeyProvider
      description: >-
        Providers for which an organisation can bring its own API key.


        Values match the ``provider`` column and the ``LLMProvider`` values used
        by

        the chatbot LLM client. The Secret Manager payload is always

        ``{"api_key": "<key>"}``. Kept separate from
        ``common.secrets.SecretType`` so

        BYO LLM keys never mix with the generic organisation Secrets subsystem.
    StandardStatusReply:
      properties:
        status:
          type: string
          title: Status
          description: The status of the operation. Always one of 'success' or 'failure'.
          examples:
            - success
            - ''
        error:
          type: string
          title: Error
          description: The error message, if any. Empty string if none.
          examples:
            - ''
            - Permission denied
      type: object
      required:
        - status
        - error
      title: StandardStatusReply
      description: >-
        A standard reply for many of our calls which has a 'status'
        ('success/failure') field and an 'error' field for failures.


        Attributes:

        - **status**: The status of the operation. Always one of 'success' or
        'failure'.

        - **error**: The error message, if any. Empty string if none.
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
  securitySchemes:
    HTTPBearer:
      type: http
      scheme: bearer

````