-
-
Notifications
You must be signed in to change notification settings - Fork 11.7k
[Feature] User Info V2 Endpoint #23437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
yuneng-jiang
merged 5 commits into
litellm_internal_dev_03_12_2026
from
litellm_user-info-endpoint-v2-24cc
Mar 13, 2026
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
81e3a2e
feat: add /v2/user/info endpoint - lightweight user info with RBAC
cursoragent 679b8fd
test: add unit tests for /v2/user/info endpoint and route checks
cursoragent d03404d
feat(ui): add userGetInfoV2 networking function and migrate useCurren…
cursoragent 7737e9c
feat(ui): migrate user_dashboard.tsx and user_info_view.tsx to /v2/us…
cursoragent cd1b31b
fix: resolve N+1 query, double-fetch, and silent error bugs in _check…
cursoragent File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
prisma_client is NonereturnsNone, causing misleading 404When
prisma_client is None,_check_user_info_v2_accessreturnsNone. The caller (user_info_v2) treatsNoneas "access denied / user not found" and raises a404. However,user_info_v2already guards against this with its ownif prisma_client is None: raise HTTPException(500)check before calling this function.The issue is that
_check_user_info_v2_accessis a standalone helper function. If it is ever called from a context that does not first checkprisma_client, a DB-unavailable condition would silently produce aNonereturn indistinguishable from a legitimate "access denied" result.Consider raising an exception here to make the failure loud: