[Fix] Proxy: end user cost tracking in the responses API #15124
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Title
Fix end user cost tracking in the responses API
Relevant issues
Fixes #13860
Pre-Submission checklist
Please complete all items before asking a LiteLLM maintainer to review your PR
tests/litellm/
directory, Adding at least 1 test is a hard requirement - see detailsmake test-unit
Screenshot of tests passing locally:

Type
🐛 Bug Fix
✅ Test
Changes
See #13860: cost tracking for end users didn't work for the responses API (but it did work for completions API) because the end user ID was set in the
litellm_metadata
field, not in themetadata
field.This PR checks both fields using the already existing
get_litellm_metadata_from_kwargs
helper function.