Current Version: v2.33.4

This changelog covers what has changed in the WhatsApp Business API client and AWS Templates.


Software Version Details

WhatsApp Business API for On-premise


Expires on Sep 2, 2021

WhatsApp Business API for AWS

Template version: 2.3.5

Expires on Sep 2, 2021



Must be 5.7.xx. Higher versions of this are not currently supported.



Versions 9.5.x, 9.6.x, and 10.x are currently supported.


At least version 18.04. Not including version 19.03.7.

Version 18.04 is required starting with v2.33


Any recent version

Ideally it should support any recent version.

WhatsApp Business API Client

Deprecated versions are not supported anymore and will soon not be allowed to send messages. Please keep your WhatsApp Business API Client installation updated.

Version Date Introduced Available Until

v2.33.4 CURRENT

Mar 10, 2021

Sep 2, 2021


Feb 23, 2021

Aug 21, 2021


Nov 13, 2020

May 12, 2021


Oct 20, 2020

Apr 18, 2021


Blocking Vs. Non-Blocking

Blocking updates are ones in which the Coreapp will suffer downtime while upgrading using the db-upgrade service. Non-blocking updates are ones in which the Coreapp should continue to run when upgrading using the db-upgrade service. You can only use the db-upgrade service to upgrade to a version >= 2.23.* from your current version.

Future Deprecations

The following fields are scheduled to be deprecated in future versions of the API:

WhatsApp Business API Client Change Details

Mar 10, 2021 (v2.33.4)

  • [Fixed] Webhook notifications for delete message events are sent to the business successfully.

Feb 23, 2021 (v2.33.3)

General Updates

  • All the docker images are now running Ubuntu 20.04. External libraries are all using latest version: php 7.4, openSSL 1.1.1, and Lighttpd 1.4.55.
  • [Deprecation] The WhatsApp Web Business Tool (deprecated since v2.29.1) will no longer be available through the Webapp URL. Postman is now the recommended way of accessing the REST API.
  • [Fixed] Security vulnerabilities within the Grafana monitoring instance.

In-Thread Context for ads that Click to WhatsApp

Starting April 21, 2021, as part of API v2.33, businesses will have access to the In-Thread Context feature for ads that click to Whatsapp. With In-Thread Context, a consumer can easily reference the ad they tapped on, and a business can understand which messages come from which ads, making the first interaction more convenient, personal and efficient.

Initial tests have shown In-Thread Context to increase the number of conversations and reduce the cost per conversation.

In order to enable In-Thread Context, the business or Business Service provider that is hosting API v2.33 needs to update their inbound webhooks integration to read a new 'referral' property added to inbound messages by April 21.

After April 21, consumers will be able to send the In-Thread Context via message attachment, containing the header, body image and video related to the ad.

If the advertiser does not complete the above updates by April 21, they will not be able to receive the attachment, and will miss important context on what the customer is messaging about. The consumer will see the ad context, and will expect the business to as well.

Conversation-based pricing

Since February 1, 2021, we have been testing a new pricing model for the WhatsApp Business API that impacts businesses messaging users with a Mexico phone number.

To support this effort, some message webhooks notifications now include the new conversation and pricing objects —only messages with status sent, delivered, and read are impacted. For more information, see Message Status Notifications.

Nov 13, 2020 (v2.31.5)

  • [Fixed] Receiving messages with fields exceeding expected limits is handled correctly.
  • [Fixed] /v1/settings/application response to display the config setting for automatic garbage collection

Oct 20, 2020 (v2.31.4)

  • A stricter version expiry has been enforced beginning with this version and for all previous versions.
  • Identity change notification
    • Businesses using the WhatsApp Business API can choose to be notified when there has been a potential update to the identity of a user with whom they are communicating. This gives businesses a signal that the person behind the account may have changed so a business can verify that they are sending information to the right number.
    • If a business opts in to this feature, they will be informed when they receive messages from WhatsApp accounts where the person controlling the account may have changed and will be blocked from sending messages to those accounts until the business acknowledges receipt of the signal and they feel it is safe to continue communications. This will protect the business and their customers from leaking sensitive information.
    • Please review best practices to enable integration for this feature: Understanding Identity Change for WhatsApp Business
  • [Fixed] Highly Structured Message packs download issue
  • [Fixed] Backup/Restore API security issue

Amazon Web Services Templates

Current Version: 2.3.5

What's included in the Amazon Web Services (AWS) - Cloud Formation (CFN) templates:

Release Version Date Introduced Changes


Mar 26, 2020

Change details


Jan 29, 2020

Change details


Aug 19, 2019

Change details


Sep 3, 2018

Change details

Release 2.3.5

Template URLs




  • Support configurable RDS parameters: storage type, multi-AZ, IOPS, engine version
  • Support Mumbai region
  • Add support for M5 level EC2 instances and M5 level DB instance class
  • Support configurable EBS volume size
  • Update the default value of DB Idle Connection Timeout to 180000 milliseconds

Release 2.3.4

Template URLs




  • Security improvements were made

Release 2.3.3

Template URLs




  • All CFN templates are now available in the new S3 bucket
  • EC2 instance is now launched from a marketplace CentOS 7 AMI
  • Removed unsupported EC2 instance type from the business API client template
  • EC2 instance is now equipped with cron jobs for maintenance work (Webapp/Coreapp log rotate, ECS agent update)
  • Use General Purpose SSD as the RDS instance storage in staging environment, now it’s the same as production environment
  • Removed unused CloudWatch alarms

Release 2.3.1

Template URLs

  • Enterprise:
  • DB:
  • Lambda:
  • Network:




  • Support for new regions (Seoul, Singapore & Tokyo)

Known Issues

DetailsFirst present inFixed in

Using dbupgrade-compose.yml to upgrade MySQL to v2.27.8 may fail



Potential memory leaks



Video preview thumbnails are not correctly generated on the receivers phone client

> v2.23.x


More database connections than necessary are opened

> v2.25.x