Current Version: v2.23.5

This changelog covers what has changed in the WhatsApp Business API Client.


Software Version Details

WhatsApp Business API for On-premise


Expires on Dec 18, 2019

WhatsApp Business API for AWS

Template version: 2.3.1

Expires on Dec 18, 2019



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.

Docker, Postman

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.23.5 CURRENT

Jun 18, 2019

Dec 18, 2019


Apr 29, 2019

Oct 29, 2019


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.

Jun 18, 2019 (v2.23.5)

  • [Fixed] WhatsApp Web Business Tool not working in Multiconnect mode
  • Upload media file size now 100MB
  • Disallow setting shards for single instance
  • Improved error handling while
    • Setting shards
    • Setting two-factor verification
    • Sending message templates
  • Oncall pager error messages improved for "structure unavailable errors"
  • "Mark messages as read" now includes all readable message types

Apr 29, 2019 (v2.23.4)

If you are using High Availability/Multiconnect setup, you will see "Bad response received from health check" error in WhatsApp Web Business Tool when you use v2.23.4.

This is a known issue, and we are working hard to fix it. This doesn't affect other functionalities such as sending messages or checking contact via the WhatsApp Business API, yet we advise you NOT to use/upgrade to v2.23.4 if you are using High Availability/Multiconnect setup and WhatsApp Web Business Tool. Single instance setups will NOT be affected.

Breaking Changes

  • callback_requests replaced with callback_requests_duration_ms_count and callback_requests_duration_ms_sum
  • metric out_message_received_by_server, out_message_received_by_target, out_message_received_by_target_read, out_message_sent replaced with out_message_status
  • Upgrade Prometheus/Grafana containers to 2.23+ to enable monitoring for new metrics

Security Advisory

The following security vulnerabilities impact v2.23.4 images. The next patch release will include fixes.


Amazon Web Services Templates

The most recent version of the template is 2.3.1.

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

Release Version Date Introduced Changes


Sep 3, 2018

Change details


Aug 22, 2018

May 18, 2018 (Beta)

Change details


April 26, 2018

Change details

Release 2.3.1

Template URLs:

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




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

Release 2.3.0

Template URLs:

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


It's recommended to use WhatsApp Business API client version v2.18.20 or later. This template might work with prior releases, though we don't recommend it.


  • Multiconnect feature is now available with this template. Please follow the multiconnect guide to learn more and setup.

Release 2.2.1

Template URLs:

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


This template requires WhatsApp Business API client version v2.18.14 or later. This template will not work with prior releases.


  • Support for a configurable log driver for containers. The default log driver is json-file, which stores the logs as a JSON file on the hosts (EC2) where containers are run. This template also provides an option to configure awslogs, where all container logs are streamed to CloudWatch. This makes all logs available in one place. When the awslogs option is selected, the container logs will not be available on the EC2 hosts. However, the log files inside a container will continue to exist.
  • Added all SSL parameters — SSL certificate, SSL key and SSL CA. SSL CA support was added in the 2.2.0 release, but the description is rephrased to avoid ambiguity.