Skip to main content

Overview

User management endpoints allow you to create and manage users with individual budgets, access control, and usage tracking.

Create User

POST /user/new

Create a new user.

Request Body

string
required
Unique identifier for the user.
string
User’s email address.
string
User role.Options: "proxy_admin", "proxy_admin_viewer", "internal_user", "internal_user_viewer", "team", "customer"
array
Teams this user belongs to.
number
Maximum spending limit for the user in USD.
array
Models this user can access.
integer
User-specific tokens per minute limit.
integer
User-specific requests per minute limit.
string
Budget reset period.
object
Custom metadata for the user.

Response

string
The created user ID.
string
User email.
string
User role.
array
Teams the user belongs to.
number
Budget limit.

Example


List Users

GET /user/list

List all users.

Query Parameters

string
Filter by team ID.
string
Filter by user role.

Response

array
Array of user objects.

Example


Get User Info

GET /user/info

Get detailed information about a specific user.

Query Parameters

string
required
The user ID to query.

Response

string
User identifier.
string
User email.
string
User role.
array
Teams the user belongs to.
number
Current spend.
number
Budget limit.
array
Accessible models.
array
API keys associated with this user.

Example


Update User

POST /user/update

Update an existing user.

Request Body

string
required
The user ID to update.
string
Update user email.
string
Update user role.
array
Update teams.
number
Update budget limit.
array
Update accessible models.
integer
Update TPM limit.
integer
Update RPM limit.

Example


Delete User

POST /user/delete

Delete a user.

Request Body

array
required
Array of user IDs to delete.

Example


User Roles

LiteLLM supports different user roles with varying permissions:

Admin Roles

role
Full admin access to the proxy.
  • Can manage all keys, teams, and users
  • Can view all spend and usage
  • Can modify proxy settings
role
View-only admin access.
  • Can view all keys, teams, and users
  • Can view all spend and usage
  • Cannot make changes

Internal User Roles

role
Standard internal user.
  • Can create/view/delete their own keys
  • Can view their own spend
  • Limited to their assigned teams and models
role
View-only internal user.
  • Can view their own keys
  • Can view their own spend
  • Cannot create or delete keys

Other Roles

role
Team-level access (used for JWT auth).
role
External customer access.

Complete Example

User Budget Tracking

How User Budgets Work

  1. Individual budgets: Each user has their own budget limit
  2. Spend tracking: All requests made by user’s keys are tracked
  3. Budget enforcement: Requests rejected when user budget exceeded
  4. Budget reset: Can reset daily, monthly, or never

User + Team Budgets

Users can belong to teams and have individual budgets: