fix(proxy): include litellm_model_table in GET /v2/team/list

[yassin-berriai]

TLDR

Problem this solves:

• GET /v2/team/list always returns litellm_model_table: null for active teams
• So a team's model_aliases can never be read back from this endpoint

How it solves it:

• Add the missing include={"litellm_model_table": True} to the active-team find_many query in list_team_v2
• Deliberately leave the deleted-team find_many alone: LiteLLM_DeletedTeamTable has no such relation in the schema, so this include would raise a database error there

User Flow

Before: an operator listing teams through the API never sees a team's configured model aliases, even though they are stored and routing correctly

1. They set model_aliases on a team, e.g. via POST /team/update with {"team_id": "<id>", "model_aliases": {"my-fast-model": "gpt-4o"}}
2. They call GET /v2/team/list?team_id=<id>
3. The returned team object always shows "litellm_model_table": null, even though the alias exists and routes correctly

After: the same list call reflects the real state

1. They set model_aliases on a team the same way
2. They call GET /v2/team/list?team_id=<id>
3. The returned team object now shows "litellm_model_table": {"id": ..., "model_aliases": {"my-fast-model": "gpt-4o"}, ...}, matching what GET /team/info and GET /team/list already returned correctly

Relevant issues

Related to #26312 (litellm_model_table read back as null). That issue was about /team/info, and was fixed there and on /team/list by #33047; this PR closes the same gap on /v2/team/list, which #33047 didn't touch.

Linear ticket

Pre-Submission checklist

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

• I have added meaningful tests
• The handful of test files covering my change pass locally, e.g. uv run pytest tests/test_litellm/<your_test_file>.py -v. Leave the suites (make test-unit-*, make test-unit) to CI: it finishes in ~15 minutes where a laptop takes an hour or more
• My PR passes all required CI/CD checks (e.g., lint, schema.d.ts sync check, etc.)
• My PR's scope is as isolated as possible; it only solves 1 specific problem
• I have received a Greptile Confidence Score of at least 4/5 before requesting a maintainer review (Greptile reviews automatically once the PR is opened; only comment @greptileai to re-request a review after pushing changes)

Delays in PR merge?

If you're seeing a delay in your PR being merged, ping the LiteLLM Team on Slack (#pr-review).

Screenshots / Proof of Fix

Ran the proxy locally against a real Postgres (python litellm/proxy/proxy_cli.py --config <config> --use_v2_migration_resolver).

Before (68cfe16)

1. curl -X POST http://127.0.0.1:14099/team/new -H "Authorization: Bearer sk-1234" -H "Content-Type: application/json" -d '{"team_alias": "v2team-repro-before", "models": ["fake-model"], "model_aliases": {"my-fast-model": "fake-model"}}' -> team_id=4572ff65-5c2a-4dd9-bf1e-57dfd3faa933
2. curl "http://127.0.0.1:14099/v2/team/list?team_id=4572ff65-5c2a-4dd9-bf1e-57dfd3faa933" -H "Authorization: Bearer sk-1234" returns:

   {"team_alias":"v2team-repro-before","team_id":"4572ff65-5c2a-4dd9-bf1e-57dfd3faa933","model_id":1,"litellm_model_table":null, ...}

   model_aliases is unreadable from this endpoint even though it was just set

After (aab515d)

1. curl -X POST http://127.0.0.1:14199/team/new -H "Authorization: Bearer sk-1234" -H "Content-Type: application/json" -d '{"team_alias": "v2team-final-active", "models": ["fake-model"], "model_aliases": {"my-fast-model": "fake-model"}}' -> team_id=1c109696-4d2c-4903-9527-3c58cae33eed
2. curl "http://127.0.0.1:14199/v2/team/list?team_id=1c109696-4d2c-4903-9527-3c58cae33eed" -H "Authorization: Bearer sk-1234" returns litellm_model_table populated:

   {"id": 1, "model_aliases": {"my-fast-model": "fake-model"}, "created_by": "default_user_id", ...}

3. Sanity check for the scoping decision above: curl -X POST http://127.0.0.1:14199/team/delete -d '{"team_ids": ["1c109696-4d2c-4903-9527-3c58cae33eed"]}' then curl "http://127.0.0.1:14199/v2/team/list?status=deleted" -> HTTP 200 with the deleted team listed, confirming the deleted-team branch (which never gets the include) still works

Type

🐛 Bug Fix

Caveats (if any)

Low

• Scope is limited to the active-team branch of /v2/team/list. Deleted teams still can't show model_aliases from this endpoint (LiteLLM_DeletedTeamTable has no relation to join), same as before this PR; /team/info and /team/list (non-deleted) were already fixed by fix: show and allow editing team model aliases after team creation #33047

Final Attestation

• The tests check the right things, including the edge cases, and regressions in the respective real-world customer use-cases are not possible after this PR

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[greptile-apps]

Greptile Summary

The PR now eagerly loads litellm_model_table when listing active teams while leaving deleted-team queries unchanged because their table has no corresponding relation.

• Adds the model-table relation include to the active /v2/team/list query.
• Adds regression coverage confirming that model aliases survive response conversion.
• Confirms the deleted-team branch does not request the unsupported relation.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
litellm/proxy/management_endpoints/team_endpoints.py	Adds the required relation include only to the active-team query, resolving the prior failure without breaking deleted-team listings.
tests/test_litellm/proxy/management_endpoints/test_team_endpoints.py	Adds endpoint-level regression coverage demonstrating that included model aliases are exposed in the returned team object.

_{Reviews (2): Last reviewed commit: "fix(proxy): drop invalid litellm_model_t..." | Re-trigger Greptile}

[codspeed]

Merging this PR will not alter performance

✅ 31 untouched benchmarks

---

_{Comparing litellm_v2_team_list_model_aliases_include (aab515d) with litellm_internal_staging (97cac0b)¹}

Footnotes

1. No successful run was found on litellm_internal_staging (3fadcd7) during the generation of this report, so 97cac0b was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[yassin-berriai]

@greptileai Confirmed and fixed: dropped the include on the deleted-team query (invalid relation there), verified live against Postgres. Please re-review head aab515d.