Skip to main content
DELETE
Delete Organisation Llm Key

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

Api-key
string | null

Path Parameters

provider
enum<string>
required

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.

Available options:
openai,
anthropic,
google,
xai,
openrouter

Response

Successful Response

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.
status
string
required

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

Examples:

"success"

""

error
string
required

The error message, if any. Empty string if none.

Examples:

""

"Permission denied"