Issue Station
Sign In
Tools hereToolbox

litellm - 💡(How to fix) Fix [Feature]: Create separate OpenAPI specs for Management API and LLM APIs [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#26679•Fetched 2026-04-29 06:12:55
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
AccessRichHAccessRichH
Participants
AccessRichHAccessRichH
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

The Feature

I would like LiteLLM to provide a distinction between the Management API and the LLM API, via the OpenAPI spec.

This is particularly useful in the Multi-Region with Global Control plane model.

Motivation, pitch

Context:

  • The LiteLLM OpenAPI Spec is huge at around 700ish operations.
  • We run LiteLLM behind Azure API Management

Most of my DEV teams will only need access to the LLM API subset of those operations, so I'd like to be able to expose documentation to them at that level, to reduce their context to something more appropriate.

Additionally, this would make a material difference in how I expose the LLM APIs via APIM, as I can logically separate and control the LLM API and the underlying regional workers without replicating huge sections of the API unnecessarily.

What part of LiteLLM is this about?

Proxy

LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?

No

Twitter / LinkedIn details

No response

extent analysis

TL;DR

Update the OpenAPI spec to separate the Management API and LLM API for better documentation and access control.

Guidance

  • Review the existing OpenAPI spec and identify the operations that belong to the Management API and LLM API.
  • Consider creating separate OpenAPI spec files or tags for each API to facilitate distinction and documentation.
  • Evaluate the current Azure API Management setup to determine how to logically separate and control access to the LLM API and regional workers.
  • Assess the potential impact on DEV teams and their access to the LLM API subset of operations.

Notes

The solution may require updates to the LiteLLM Proxy component and the OpenAPI spec, as well as changes to the Azure API Management configuration.

Recommendation

Apply workaround by creating separate OpenAPI spec files or tags for each API, as updating the existing spec may be complex and time-consuming.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#file not found#serialization error#model compatibility#GPU setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING