Question: Will Evolution API 2.4.0 provide the quoted message ID for replies to media messages?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- typescript
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- TypeScript
- Stars
- 9.7k
- Forks
- 7.3k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from evolution-foundation/evolution-api
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
evolution-foundation/evolution-api#2723 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
evolution-foundation/evolution-api#2704 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
evolution-foundation/evolution-api#2702 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
evolution-foundation/evolution-api#2700 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
evolution-foundation/evolution-api#2675 ·
Maintainers usually reply within 1 day
All issues in evolution-foundation/evolution-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openedx/frontend-app-authoring#3274 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area/documentation status/need-triage
Difficulty 1/5 Under an hour Newbie friendliness 95/100
google-gemini/gemini-cli#29548 ·
Maintainers usually reply within 1 day
-
sdk-typescript vector-store
Difficulty 2/5 Half a day Newbie friendliness 82/100
mem0ai/mem0#7495 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day