You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the key query is not provided on a request to /key/info, I think LiteLLM should return the info about the current key being used in the Authorization: Bearer sk-... header.
@Manouchehri that wouldn't solve my problem in #1614 of not being able to display user-friendly keys to users
Scenario: So app owner goes to your dashboard -> you get all the keys associated with their user id -> you display them by the alias'es specified by them / abbreviated keys -> they click on one -> see the logs of their token usage and cost logs for the app -> identify which end-users might be driving high-spend
The Feature
If the
key
query is not provided on a request to/key/info
, I think LiteLLM should return the info about the current key being used in theAuthorization: Bearer sk-...
header.Motivation, pitch
imo this reduces the need for #1614.
Twitter / LinkedIn details
https://www.linkedin.com/in/davidmanouchehri/
The text was updated successfully, but these errors were encountered: