The /audio-to-text endpoint document is error #21078

Open
opened 2026-02-21 20:10:34 -05:00 by yindo · 4 comments
Owner

Originally created by @yaxiAndcc on GitHub (Dec 16, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.10

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

use /audio-to-text endpoint transfer webpm file

✔️ Expected Behavior

The /audio-to-text endpoint is documented as supporting the following audio formats:['mp3', 'mp4', 'mpeg', 'mpga', 'm4a', 'wav', 'webm']
However, the actual code implementation only supports:{"mp3", "m4a", "wav", "amr", "mpga"}
Key discrepancies identified:
Formats listed in docs but missing in code: mp4, mpeg, webm
Format present in code but absent from docs: amr

Actual Behavior

return {
"code": "unsupported_audio_type",
"message": "Audio type not allowed.",
"status": 415
}

Originally created by @yaxiAndcc on GitHub (Dec 16, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.10 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce use /audio-to-text endpoint transfer webpm file ### ✔️ Expected Behavior The /audio-to-text endpoint is documented as supporting the following audio formats:['mp3', 'mp4', 'mpeg', 'mpga', 'm4a', 'wav', 'webm'] However, the actual code implementation only supports:{"mp3", "m4a", "wav", "amr", "mpga"} Key discrepancies identified: Formats listed in docs but missing in code: mp4, mpeg, webm Format present in code but absent from docs: amr ### ❌ Actual Behavior return { "code": "unsupported_audio_type", "message": "Audio type not allowed.", "status": 415 }
yindo added the 📚 documentationstale labels 2026-02-21 20:10:34 -05:00
Author
Owner

@andesign31 commented on GitHub (Dec 23, 2025):

"Hi team! I'm a Technical Writer and I'd like to help with the detailed documentation for the Sandbox service. I can help structure the architecture overview, configuration steps, and security limitations. May I take this issue?"

@andesign31 commented on GitHub (Dec 23, 2025): "Hi team! I'm a Technical Writer and I'd like to help with the detailed documentation for the Sandbox service. I can help structure the architecture overview, configuration steps, and security limitations. May I take this issue?"
Author
Owner

@lantianliu5-alt commented on GitHub (Jan 12, 2026):

"Hi team! I'm a Technical Writer and I'd like to help with the detailed documentation for the Sandbox service. I can help structure the architecture overview, configuration steps, and security limitations. May I take this issue?"

ok ok

@lantianliu5-alt commented on GitHub (Jan 12, 2026): > "Hi team! I'm a Technical Writer and I'd like to help with the detailed documentation for the Sandbox service. I can help structure the architecture overview, configuration steps, and security limitations. May I take this issue?" ok ok
Author
Owner

@lantianliu5-alt commented on GitHub (Jan 12, 2026):

Self Checks

  • I have read the Contributing Guide and Language Policy.[x] This is only for bug report, if you would like to ask a question, please head to Discussions.[x] I have searched for existing issues search for existing issues, including closed ones.[x] I confirm that I am using English to submit this report, otherwise it will be closed.[x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)[x] Please do not modify this template :) and fill in all the required fields.

Dify version

1.10

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

use /audio-to-text endpoint transfer webpm file

✔️ Expected Behavior

The /audio-to-text endpoint is documented as supporting the following audio formats:['mp3', 'mp4', 'mpeg', 'mpga', 'm4a', 'wav', 'webm'] However, the actual code implementation only supports:{"mp3", "m4a", "wav", "amr", "mpga"} Key discrepancies identified: Formats listed in docs but missing in code: mp4, mpeg, webm Format present in code but absent from docs: amr

Actual Behavior

return { "code": "unsupported_audio_type", "message": "Audio type not allowed.", "status": 415 }

Have you solved it?

@lantianliu5-alt commented on GitHub (Jan 12, 2026): > ### Self Checks > * [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542).[x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general).[x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones.[x] I confirm that I am using English to submit this report, otherwise it will be closed.[x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)[x] Please do not modify this template :) and fill in all the required fields. > > ### Dify version > 1.10 > > ### Cloud or Self Hosted > Self Hosted (Docker) > > ### Steps to reproduce > use /audio-to-text endpoint transfer webpm file > > ### ✔️ Expected Behavior > The /audio-to-text endpoint is documented as supporting the following audio formats:['mp3', 'mp4', 'mpeg', 'mpga', 'm4a', 'wav', 'webm'] However, the actual code implementation only supports:{"mp3", "m4a", "wav", "amr", "mpga"} Key discrepancies identified: Formats listed in docs but missing in code: mp4, mpeg, webm Format present in code but absent from docs: amr > > ### ❌ Actual Behavior > return { "code": "unsupported_audio_type", "message": "Audio type not allowed.", "status": 415 } Have you solved it?
Author
Owner

@dosubot[bot] commented on GitHub (Feb 12, 2026):

Hi, @yaxiAndcc. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a discrepancy between the /audio-to-text endpoint documentation and its actual implementation regarding supported audio formats.
  • Documentation lists mp4, mpeg, and webm as supported, but the code supports mp3, m4a, wav, amr, and mpga instead.
  • The amr format is supported in code but missing from the documentation.
  • A community member offered to help improve the documentation, and a maintainer acknowledged the issue with reproduction details.
  • No fix or update has been provided yet.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
  • Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Feb 12, 2026): Hi, @yaxiAndcc. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a discrepancy between the /audio-to-text endpoint documentation and its actual implementation regarding supported audio formats. - Documentation lists mp4, mpeg, and webm as supported, but the code supports mp3, m4a, wav, amr, and mpga instead. - The amr format is supported in code but missing from the documentation. - A community member offered to help improve the documentation, and a maintainer acknowledged the issue with reproduction details. - No fix or update has been provided yet. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open. - Otherwise, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#21078