fix: pass response_format in TTS API requests and map to correct content_type#87
Merged
fix: pass response_format in TTS API requests and map to correct content_type#87
Conversation
…ent_type OpenAI-compatible TTS providers now extract response_format from kwargs, include it in the API payload, and use the correct MIME type for AudioResponse.content_type. Previously response_format was never sent and content_type was always hardcoded to audio/mp3, causing failures when providers return non-MP3 audio (e.g. WAV from mlx-audio/Kokoro). Closes #86
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
leejangthegreat
added a commit
to leejangthegreat/esperanto
that referenced
this pull request
Feb 21, 2026
leejangthegreat
added a commit
to leejangthegreat/esperanto
that referenced
this pull request
Feb 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
response_formatfrom kwargs (defaulting to"mp3"), include it in the API payload, and map it to the correct MIME type forAudioResponse.content_typeresponse_formatwas never sent andcontent_typewas always hardcoded to"audio/mp3", causing failures when providers return non-MP3 audio (e.g. WAV from mlx-audio/Kokoro)Closes #86
Test plan
response_formatis included in payload andcontent_typeis mapped correctly (OpenAI + OpenAI-compatible)response_format="wav"