[Feature] Bulk Update Keys Endpoint

[yuneng-jiang]

Relevant issues

This PR adds a /key/bulk_update endpoint to the keys management list of endpoints. The use case for this is inside the UI, many admins want to bulk update keys when teams / budgets change. Currently, they need to use the API or do so 1-by-1 on the UI, which is bad UX

The end goal for this endpoint is to allow bulk updates for keys in a single endpoint. This only supports updating max_budget, team_id, and tags currently and should be treated as a beta endpoint.

Spec:

{
  "keys": {
    "key_id": string;
    "team_id": string;
    "tags": string[];
  }
}

This is a best effort bulk update, any failing requests will not block the entire request from going through, and keys that can be updated will be updated.

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
• My PR passes all unit tests on make test-unit
• My PR's scope is as isolated as possible, it only solves 1 specific problem

CI (LiteLLM team)

CI status guideline:

• 50-55 passing tests: main is stable with minor issues.
• 45-49 passing tests: acceptable but needs attention
• <= 40 passing tests: unstable; be careful with your merges and assess the risk.

• Branch creation CI run
  Link:

• CI run for the last commit
  Link:

• Merge / cherry-pick CI run
  Links:

Type

🆕 New Feature
✅ Test

Changes

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
litellm	Error		Jan 27, 2026 10:08pm