litellm - ✅(Solved) Fix [Bug]: Missing `segments` in OVH audio transcription response [2 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#25633Fetched 2026-04-14 05:38:28
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Participants
Timeline (top)
cross-referenced ×2labeled ×2referenced ×1

Fix Action

Fixed

PR fix notes

PR #25648: Allow segments and language in ovhcloud response in case of response_format=verbose_json requests

Description (problem / solution / changelog)

Relevant issues

Fixes #25633

Pre-Submission checklist

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

  • I have Added testing in the tests/test_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
  • I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

Delays in PR merge?

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

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:

Screenshots / Proof of Fix

<!-- Include screenshots, screen recordings, or log output demonstrating that your changes work as expected. For bug fixes: show reproduction before the fix and passing behavior after. For new features: show the feature working end-to-end. For UI changes: include before/after screenshots. -->

Type

<!-- Select the type of Pull Request --> <!-- Keep only the necessary ones -->

🐛 Bug Fix ✅ Test

Changes

Changed files

  • litellm/llms/ovhcloud/audio_transcription/transformation.py (modified, +5/-0)
  • tests/test_litellm/llms/ovhcloud/test_ovhcloud_audio_transcription_transformation.py (modified, +38/-0)

PR #25651: fix(ovhcloud): preserve segments/words/language in verbose_json transcription response

Description (problem / solution / changelog)

Problem

Fixes #25633

When using with the OVHCloud Whisper endpoint, the API returns a full verbose response containing segments, words, language, duration, etc. — but only the text field was being returned to callers.

Root cause: OVHCloudAudioTranscriptionConfig.transform_audio_transcription_response manually extracted only the text (or transcript) field, discarding everything else.

Fix

Mirror the approach used by the OpenAI Whisper implementation: pass the full response JSON to TranscriptionResponse(**response_json) so all OpenAI-compatible fields are preserved.

A normalisation step handles the case where OVHCloud returns transcript instead of text (backwards compatible).

Changes

  • litellm/llms/ovhcloud/audio_transcription/transformation.py — updated transform_audio_transcription_response to pass through all fields
  • tests/test_litellm/llms/ovhcloud/test_ovhcloud_audio_transcription_transformation.py — added unit tests covering:
    • verbose_json response with segments preserved
    • plain-text response (no regression)
    • transcript field normalised to text

Testing

The new unit tests run without an API key and cover the fixed code path directly.

Changed files

  • litellm/llms/ovhcloud/audio_transcription/transformation.py (modified, +18/-2)
  • tests/test_litellm/llms/ovhcloud/test_ovhcloud_audio_transcription_transformation.py (modified, +73/-0)
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

If i use the response_format verbose_json for the speech to text api with an OVH Provider i only get the text response without the expected segments. The request looks correct. Only the response mapping doesn't contain the segments mapping

Steps to Reproduce

  1. Use OVH whisper Model
  2. use response_format verbose_json
  3. got response with text only. segments is missing

Relevant log output

What part of LiteLLM is this about?

Proxy

What LiteLLM version are you on ?

v1.82.3

Twitter / LinkedIn details

No response

extent analysis

TL;DR

The issue might be resolved by checking the response mapping configuration for the OVH provider in the LiteLLM Proxy.

Guidance

  • Verify the response mapping configuration for the OVH provider to ensure it includes the segments field.
  • Check the documentation for the OVH whisper Model and verbose_json response format to confirm that segments is a supported field.
  • Review the LiteLLM Proxy code to see if there are any specific handling or parsing rules for the OVH provider's response format.
  • Test the same request with a different provider to see if the issue is specific to OVH.

Notes

The issue seems to be specific to the OVH provider and the verbose_json response format, so the solution may depend on the specific configuration and implementation of the LiteLLM Proxy.

Recommendation

Apply workaround: Check and adjust the response mapping configuration for the OVH provider to include the segments field, as this is the most likely cause of the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING