Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Question: Will Evolution API 2.4.0 provide the quoted message ID for replies to media messages?

Aberta
  • Algo errado?
#2,724 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 5 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
typescript
Domínio
api, backend

Direção de pesquisa

Start by inspecting the MESSAGES_UPSERT webhook handling and the quoted-message or message-context changes mentioned for version 2.4.0. Compare an incoming text reply to an image with the expected contextInfo, stanzaId, or quotedMessage fields, and confirm whether replies to imageMessage and documentMessage expose the original ID without extra configuration.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

bug
Welcome!
  • Yes, I have searched for similar issues on GitHub and found none.
What did you do?

Hi Evolution API team,

We are currently using Evolution API 2.3.7 and we have a use case that depends on identifying the original media message when a customer replies to an image on WhatsApp.

Scenario
A customer sends an image through WhatsApp.
We receive and store the image message ID from the Evolution API webhook.

Later, the customer uses WhatsApp's Reply feature on that specific image and sends a text message, for example:

15x21 glossy

In our application, we need to identify which original image message the customer replied to.

Ideally, the incoming webhook would provide something like the original message ID through contextInfo, stanzaId, quotedMessage, or another equivalent field.

Conceptually:

Image message
messageId = ABC123
↓
Customer replies to this image
"15x21 glossy"
↓
MESSAGES_UPSERT webhook
↓
quoted/original message ID = ABC123

With Evolution API 2.3.7, we have not been able to reliably obtain this reference from the incoming webhook.

We noticed that the 2.4.0 development/release notes include changes related to quoted messages and message context, so we would like to know:

Does Evolution API 2.4.0 now provide the ID of the original message when an incoming text message is a reply to a previously received image/media message?

If so:

Which field contains the original message ID?
Is it available in the MESSAGES_UPSERT webhook?
Does it work for replies to imageMessage, documentMessage, and other media types?
Is any specific webhook/event configuration required?

If this is not yet supported/fixed in 2.4.0, is there an existing issue or planned implementation that we can follow?

This feature would be very useful for applications that need to associate a customer's reply with a specific previously received media item.

Thank you!

What did you expect?

When a customer uses WhatsApp's Reply feature to reply to a previously received image/media message, we expect the MESSAGES_UPSERT webhook to include the ID of the original quoted message.

For example:

Original image message ID: ABC123

Customer replies to that image:
"15x21 glossy"

Expected webhook:
quoted/original message ID = ABC123

This would allow us to associate the customer's reply with the exact media message that was previously received and stored by our application.

The reference could be provided through contextInfo.stanzaId, quotedMessage, or another equivalent field.

What did you observe instead of what you expected?

With Evolution API 2.3.7, when the customer replies to a specific image using WhatsApp's Reply feature, the incoming text message is received, but we are unable to reliably obtain the message ID of the original image from the MESSAGES_UPSERT webhook.

As a result, our application receives the reply text (for example, "15x21 glossy"), but cannot determine which previously received image the customer is referring to.

We noticed that Evolution API 2.4.0 includes development changes related to quoted messages and message context, so we would also like to know whether this behavior has been fixed or changed in 2.4.0, and which field should now be used to retrieve the original quoted message ID.

Screenshots/Videos

No response

Which version of the API are you using?

Evolution API 2.3.7

What is your environment?

Windows

Other environment specifications
If applicable, paste the log output

No response

Additional Notes

No response

Linguagem predominante
TypeScript
Estrelas
9.9k
Forks
7.4k
Nenhum PR com merge em 30d

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de evolution-foundation/evolution-api

Todas as issues de evolution-foundation/evolution-api

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.