Retrieve, update, and delete individual custom LLM providers
Supports both internal (JWT) and public (API key) authentication.
Access control (layered):
Endpoints: Platform (JWT auth, uses numeric pk): GET /llm_models/custom_providers/{pk}/ - Retrieve a specific custom provider PATCH /llm_models/custom_providers/{pk}/ - Update a specific custom provider DELETE /llm_models/custom_providers/{pk}/ - Delete a specific custom provider Public API (API key auth, uses provider_id string): GET /api/providers/{provider_id}/ - Retrieve a specific custom provider PATCH /api/providers/{provider_id}/ - Update a specific custom provider DELETE /api/providers/{provider_id}/ - Delete a specific custom provider
Args (PATCH):
Returns (GET): { “id”: 123, “provider_id”: “my-custom-openai”, “provider_name”: “My Custom OpenAI Provider”, “litellm_provider_id”: “openai”, “moderation”: “filtered”, “extra_kwargs”: { “api_key”: “sk-custom-key-123”, “base_url”: “https://api.my-custom-provider.com/v1”, “temperature”: 0.7, “max_tokens”: 4096 }, “organization”: 456, “created_at”: “2024-01-15T10:30:00Z”, “updated_at”: “2024-01-15T11:00:00Z” }
Returns (PATCH): { “id”: 123, “provider_id”: “my-custom-openai”, “provider_name”: “My Updated Custom OpenAI Provider”, “extra_kwargs”: { “api_key”: “sk-updated-key-456”, “base_url”: “https://api.my-updated-provider.com/v1”, “temperature”: 0.8, “max_tokens”: 8192 }, … }