scriptoriumadmin/litellm
1
0
Fork 0
mirror of https://github.com/BerriAI/litellm.git synced 2026-09-06 08:16:43 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 79

chore(ui): regenerate schema.d.ts for updated endpoint descriptions

Browse source 
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
This commit is contained in:
Devin AI 2026-08-30 07:46:45 +00:00
parent 4fb1440747
commit 36c53e1288
1 changed files with 15 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
ui/litellm-dashboard/src/lib/http/schema.d.ts generated vendored
View file

@ -16210,6 +16210,10 @@ export interface paths {
*
* Meant to optimize querying spend data for analytics for a user.
*
* Reads immutable daily spend records, which are never affected by budget resets.
* This can legitimately exceed the `spend` field returned by `/v2/user/info`, which
* is a running budget counter zeroed on every budget reset.
*
* Returns:
* (by date)
* - spend
@ -16241,6 +16245,10 @@ export interface paths {
* Get User Daily Activity Aggregated
* @description Aggregated analytics for a user's daily activity without pagination.
* Returns the same response shape as the paginated endpoint with page metadata set to single-page.
*
* Reads immutable daily spend records, which are never affected by budget resets.
* This can legitimately exceed the `spend` field returned by `/v2/user/info`, which
* is a running budget counter zeroed on every budget reset.
*/
get: operations["get_user_daily_activity_aggregated_user_daily_activity_aggregated_get"];
put?: never;
@ -21004,6 +21012,13 @@ export interface paths {
* This is the v2 replacement for /user/info, designed to avoid the "god endpoint" problem
* where the old endpoint loaded all keys and teams into memory.
*
* Note on `spend`: this is the user's running budget counter, which is zeroed by the
* budget reset job whenever `budget_reset_at` elapses (see `budget_duration`). It is NOT
* lifetime or per-period historical spend. For historical spend over a date range, use
* `/user/daily/activity` or `/user/daily/activity/aggregated`, which read immutable daily
* spend records that are never reset. The two values are expected to diverge once a
* budget reset has occurred within the queried period.
*
* Access control:
* - Proxy admins can query any user
* - Team admins can query users within their teams