-
Notifications
You must be signed in to change notification settings - Fork 5.4k
Description
📋 Bug Description
In Evolution API version 2.3.7, WhatsApp interactive messages (Buttons and Lists)
are not working correctly. Requests that previously worked in earlier versions
(e.g. 2.3.6) now fail when sending interactive payloads.
The issue affects both Buttons and List messages, causing the API to return
errors or reject the message payload.
🔄 Steps to Reproduce
- Run Evolution API version 2.3.7
- Connect a WhatsApp session (Baileys)
- Attempt to send an interactive message using Buttons or List format using POSTMAN
- Send the request via API endpoint (eg:- sendButtons/sendLists)
- Observe the API response
✅ Expected Behavior
Interactive Buttons and List messages should be sent successfully to WhatsApp
recipients, as they did in previous versions (e.g. v2.3.6), without errors.
❌ Actual Behavior
The API fails to send interactive Buttons or List messages.
The request is rejected or returns an error (e.g. 400 Bad Request / internal error),
and the message is not delivered to the recipient.
🌍 Environment
- OS: Windows 11
- Node.js version: 18.20.5
- Evolution API version: 2.3.7
- Database: PostgreSQL 14
- Connection type: Baileys
📋 Logs
{
"status": 400,
"error": "Bad Request",
"response": {
"message": [
"TypeError: this.isZero is not a function"
}
}📝 Additional Context
Buttons and List messages work correctly when downgrading to Evolution API v2.3.6.
This suggests a regression introduced in version 2.3.7.
Currently blocking interactive user flows that depend on Buttons and Lists.