Welcome!
What type of feature?
Functionality
What is the motivation for the request?
Currently, the Evolution API does not support retrieving poll results using the /chat/findMessages/ endpoint. This limitation means that if users do not capture poll responses in real time, they cannot access this information later, even though it is available through WhatsApp Web.
The requested feature aims to allow the Evolution API to fetch poll results from past messages, enabling developers to retrieve this data whenever needed, without relying on real-time capture. This enhancement would align with the existing functionality available on WhatsApp Web and improve data consistency across platforms.
Additionally, this request ties into an ongoing issue (#975), where critical fields like ctwa_clid are accessible via WhatsApp Web but are not being retrieved through the API fetch. Both these features could be tackled simultaneously to improve data retrieval capabilities.
Usage Examples
Scenario 1: A developer needs to analyze responses from a poll conducted in a group chat. With the current setup, if the developer did not capture the responses as they occurred, they are unable to retrieve the data later. This feature would allow them to fetch these results on demand.
Scenario 2: An application that aggregates poll data for analytics could use this functionality to retrospectively collect poll responses, providing more comprehensive reporting for users who may not have been online during the poll's runtime.
How should the feature be developed?
This functionality could be integrated directly into the existing /chat/findMessages/ endpoint, as it aligns with its core purpose of retrieving various message types. However, a more refined approach could be to develop a specific endpoint designed solely for poll data retrieval. This endpoint would fetch poll results based on the message ID, ensuring that developers can target and retrieve poll information precisely without affecting the performance of other message retrieval operations.
Additional Notes
While this request focuses on enabling poll data retrieval, it also highlights a broader issue regarding the availability of fields like ctwa_clid. Addressing these data consistency problems could significantly enhance the API’s reliability and functionality.
Welcome!
What type of feature?
Functionality
What is the motivation for the request?
Currently, the Evolution API does not support retrieving poll results using the /chat/findMessages/ endpoint. This limitation means that if users do not capture poll responses in real time, they cannot access this information later, even though it is available through WhatsApp Web.
The requested feature aims to allow the Evolution API to fetch poll results from past messages, enabling developers to retrieve this data whenever needed, without relying on real-time capture. This enhancement would align with the existing functionality available on WhatsApp Web and improve data consistency across platforms.
Additionally, this request ties into an ongoing issue (#975), where critical fields like ctwa_clid are accessible via WhatsApp Web but are not being retrieved through the API fetch. Both these features could be tackled simultaneously to improve data retrieval capabilities.
Usage Examples
Scenario 1: A developer needs to analyze responses from a poll conducted in a group chat. With the current setup, if the developer did not capture the responses as they occurred, they are unable to retrieve the data later. This feature would allow them to fetch these results on demand.
Scenario 2: An application that aggregates poll data for analytics could use this functionality to retrospectively collect poll responses, providing more comprehensive reporting for users who may not have been online during the poll's runtime.
How should the feature be developed?
This functionality could be integrated directly into the existing /chat/findMessages/ endpoint, as it aligns with its core purpose of retrieving various message types. However, a more refined approach could be to develop a specific endpoint designed solely for poll data retrieval. This endpoint would fetch poll results based on the message ID, ensuring that developers can target and retrieve poll information precisely without affecting the performance of other message retrieval operations.
Additional Notes
While this request focuses on enabling poll data retrieval, it also highlights a broader issue regarding the availability of fields like ctwa_clid. Addressing these data consistency problems could significantly enhance the API’s reliability and functionality.