> For the complete documentation index, see [llms.txt](https://support.whapi.cloud/help-desk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.whapi.cloud/help-desk/sending/overview-of-other-methods-for-sending/send-voice-message.md). # Send Voice message How to Send Voice Messages via WhatsApp API? You can Send a ppt audio recording to the phone number or group, But WhatsApp is sensitive to this extension, you need to be in OGG format and the **codec** should be the **opus**. {% hint style="success" %} Our API has an automatic video and audio converter for the necessary codecs compatible with WhatsApp. {% endhint %} ### How to get exactly the correct codec format? 1 - Start by sending your voice message on WhatsApp from your phone. 2 - Now, fetch the voice message's link via [/messages/list](https://whapi.readme.io/reference/getmessages). 3 - With your voice message file ID in hand, you can now send it using the [/messages/voice](https://whapi.readme.io/reference/sendmessagevoice) method. {% embed url="" %} Note, you may be interested in this article: [How to generate a waveform for a voice message](/help-desk/sending/overview-of-other-methods-for-sending/how-to-generate-a-waveform-for-a-voice-message.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.whapi.cloud/help-desk/sending/overview-of-other-methods-for-sending/send-voice-message.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.