fix(docs): Supported Endpoints page#17710
Merged
Merged
Conversation
…s slug conflict The relative link was causing Docusaurus to incorrectly associate the /supported_endpoints page with SDK Functions category instead of the actual Supported Endpoints generated-index.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Chesars
changed the title
Chesars
changed the title
|
this still doesn't fix the problem. when you click on 'all supported endpoints' - it doesn't open the page for all the proxy endpoints. it just shows me all the sdk functions (which is btw not comprehensive) 
|
Collaborator
Author
PR #17718 adds some documentation and fixes that. |
Contributor
|
oops so sorry I accidently merged this in, did not see you reviewed it @krrishdholakia feel free to revert |
Chesars
pushed a commit
to Chesars/litellm-docs
that referenced
this pull request
May 14, 2026
v3.10.0 includes the fix for facebook/docusaurus#11612 (sidebar link vs generated-index slug conflict), which is the underlying bug that BerriAI/litellm#17710 worked around.
Chesars
added a commit
to Chesars/litellm-docs
that referenced
this pull request
May 16, 2026
Reverts the workaround from BerriAI/litellm#17710. The Docusaurus slug-conflict bug is fixed in the new Docusaurus release, so the link can go back to a relative URL.
Chesars
added a commit
to Chesars/litellm-docs
that referenced
this pull request
May 16, 2026
v3.10.0 includes the fix for facebook/docusaurus#11612 (sidebar link vs generated-index slug conflict), which is the underlying bug that BerriAI/litellm#17710 worked around.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Title
Fix Supported Endpoints page showing SDK Functions instead of actual endpoints
Relevant issues
N/A
Pre-Submission checklist
tests/litellm/directory, Adding at least 1 test is a hard requirement - N/A (docs-only change)make test-unit- N/A (docs-only change)Type
🐛 Bug Fix
📖 Documentation
Changes
The
/docs/supported_endpointspage was incorrectly showing SDK Functions (completion(), embedding(), etc.) instead of the actual supported endpoints (/a2a, /audio, /batches, etc.).Root cause: Docusaurus has a bug where internal links (
/docs/...) inside a sidebar category can conflict withgenerated-indexpages that have the same slug. The link in SDK Functions pointing to/docs/supported_endpointswas causing Docusaurus to associate that page with SDK Functions context.Fix: Changed the link from relative (
/docs/supported_endpoints) to absolute URL (https://docs.litellm.ai/docs/supported_endpoints). This makes Docusaurus treat it as an external link, avoiding the slug conflict with thegenerated-index.Reference: facebook/docusaurus#11612