I’m able to deliver audio via inline mode when using a URL, but I’m encountering issues when attempting to send an audio file stored locally. The Telegram Bot API instead responds with an error. Below is a sample of the error returned:
{
"success": false,
"error": 400,
"message": "Invalid source: local audio file path is not accepted."
}
How can I modify my implementation to correctly send local audio files using inline queries?
In a similar project I worked on, I realized that the Telegram Bot API has strict constraints regarding local files, particularly when used in inline queries. My solution involved uploading the local file to a web-accessible server first and then creating references to that URL in my inline responses. This approach required an initial step of file hosting, after which the audio content was processed correctly by the API. Alternatively, if the inline approach isn’t feasible, you could consider sending the audio as an attachment using multipart form data directly in a message.
Based on my experience, the Telegram Bot API does not allow sending local files directly in inline queries. I had to work around this limitation by first uploading the file to a trusted external server that can provide a secure HTTPS URL. Once the file is accessible online, the inline query returns that URL, and Telegram processes it without issues. It is important to note that any attempts to reference local storage paths will lead to errors. This method may require additional hosting arrangements, but it reliably resolves the problem.
hey, i ran into the same issue. i ended up uploading my audio files to a server then using the provided https url in my inline queries since local paths dont work. hope this helps.