Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Permitir áudio comum com player usando ptt: false

Open
#217 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 5 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
api, backend

Research direction

The issue names the POST /send/media endpoint and the type: "audio" path, which converts files to OGG/Opus and sets PTT to true. Start from the media send handler and that conversion branch, then check whether an optional ptt field can be read and passed through. Done means ptt: false sends an MP3 as a regular audio/mpeg message, and an omitted field keeps today's behaviour. The issue asks whether maintainers would accept this, so confirm the approach before writing code.

Written by the indexing model from the issue text.

Description

enhancement
Welcome!
  • Yes, I have searched for similar requests on GitHub and found none.
What type of feature?

Functionality

What is the motivation for the request?

Olá! Preciso enviar um MP3 como áudio comum no WhatsApp,
com player dentro da conversa, sem aparecer como mensagem
de voz gravada e sem ser enviado como documento.

No código consultado, o envio com type: "audio" converte
o arquivo para OGG/Opus e define PTT como true.

Seria possível adicionar um parâmetro opcional "ptt" ao
endpoint POST /send/media?

Comportamento sugerido:

  • ptt: true: enviar como mensagem de voz.
  • ptt: false: enviar como áudio comum, preservando MP3
    e o MIME audio/mpeg.
  • Parâmetro omitido: manter o comportamento atual,
    preservando a compatibilidade.

Exemplo da requisição desejada:

{
"number": "5511999999999",
"type": "audio",
"ptt": false,
"url": "https://exemplo.com/audio.mp3"
}

Existe alguma forma de fazer isso na versão atual?
Caso não exista, vocês considerariam implementar?

Usage Examples

No response

How should the feature be developed?

No response

Additional Notes

No response

Dominant language
Go
Stars
918
Forks
488
Avg merge
5m
Merged PRs (30d)
1

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from evolution-foundation/evolution-go

All issues in evolution-foundation/evolution-go

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.