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 | Changes |
---|---|---|
| Apr 17, 2020 | |
| Apr 8, 2020 | |
| Mar 4, 2020 | |
| Feb 4, 2020 | |
| Jan 6, 2020 | |
| Nov 13, 2019 | |
| Oct 7, 2019 | |
| Sep 9, 2019 | |
| Aug 26, 2019 | |
| Sep 9, 2019 | |
| Jun 18, 2019 | |
| Apr 29, 2019 | |
| Jan 24, 2019 | |
| Nov 13, 2018 | |
| Oct 24, 2018 | |
| Sep 24, 2018 | |
| Jul 24, 2018 | |
| Jul 18, 2018 | |
| Jun 15, 2018 | |
| May 10, 2018 | |
| Apr 18, 2018 | |
| Apr 16, 2018 | |
| Apr 3, 2018 | |
| Mar 29, 2018 | |
| Mar 22, 2018 | |
| Mar 14, 2018 | |
| Mar 5, 2018 | |
| Feb 26, 2018 | |
| Feb 10, 2018 | |
| Jan 31, 2018 | |
| Jan 22, 2018 | |
| Jan 10, 2018 |
Known Issue: Using dbupgrade-compose.yml
to upgrade MySQL to v2.27.8
may fail. Refrain from using dbupgrade-compose.yml
for now. The product upgrading procedure outlined in the production setup documentation still works, but not the upgrading MySQL procedure. An upcoming patch release will address this issue.
force_check
parameter/v1/contacts
API call in async mode, the results can be posted to the callback server without having to poll the check contacts statusfallback
language policy is deprecated for sending message templateshealth
API calls to help monitor multiple deployments of WhatsApp Business API clients
health
endpoint is set to 10 per secondThe following security vulnerabilities impact the v2.25.1 Coreapp image. The next patch release will include fixes.
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.
471
, 472
, etc.) filename
in addition to the caption
field that the user will see when they attempt to download the documentfilename
provided by the sender will now also be shared in the callback in addition to the caption
fieldcallback_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
The following security vulnerabilities impact v2.23.4 images. The next patch release will include fixes.
GET /v1/settings/business/profile
to return as empty/v1/contacts
did not return info500
returned when sending JPEG images500: Internal Server Error
was returned./etc/hosts
. Please note that if WA_DB_HOSTNAME is IPV4 address, it works fine.This version has issues in both AWS and On-Premise. Please do NOT not upgrade to 2.19.3. If you want to upgrade, please use 2.19.4. If you have already upgraded to 2.19.3 with On-Premise setup it might prevent you from restarting in some cases so consider upgrading to 2.19.4 at the earliest.
format=prometheus
{ "webhooks": { "ignore_ssl_errors": true, "url": "https://webhook_endpoint" } }
WhatsApp Enterprise Application v2.18.22 is the last release that will support the legacy PHP API!
wa_id
only for valid contacts.data
and media
).type
which is the indicates the type of message.media_url_prefix
logic so that replacing "media.hostname.com"
with IP address of web container will point to incoming media file.conversation
and now using text
for message field.Version | Date Introduced | Changes |
---|---|---|
| June 20, 2018 | |
| June 12, 2018 | |
| May 10, 2018 | |
| Mar 27, 2018 | |
| Feb 16, 2018 | |
| Feb 10, 2018 | |
| Jan 23, 2018 | |
| Jan 11, 2018 | |
| Dec 21, 2017 | |
| Dec 11, 2017 | |
| Dec 6, 2017 | |
| Oct 31, 2017 | |
| Oct 1, 2017 | |
| Sept 19, 2017 | |
| Sept 18, 2017 | |
| July 31, 2017 | |
| July 25, 2017 | |
| July 10, 2017 | |
| June 21, 2017 | |
| June 10, 2017 | |
| May 11, 2017 | |
| May 1, 2017 | - |
wadockersetup
script now has an upgrade command.pass_through
to set settings script.What's included in the AWS (Amazon Web Services) - Cloud Formation (CFN) templates:
Release Version | Date Introduced | Changes |
---|---|---|
| Aug 22, 2018 May 18, 2018 (Beta) | |
| April 26, 2018 | |
| April 26, 2018 | |
| January 31, 2018 | |
| December 22nd, 2017 | |
| Sept 13th, 2017 | |
| June 23rd, 2017 |
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.
This template requires WhatsApp Business API client version v2.18.14 or later. This template will not work with prior releases.
The Lambda template is created and used for security enhancement. This stores the sensitive information securely (i.e., encrypted) in a parameter store and retrieves it inside the container. We might add more functions in future or remove it, if this is supported in CFN templates.
This template requires WhatsApp Enterprise client version v2.18.14 or later. This template will not work with prior releases.
Note: Please use experimental/beta features with caution. It's highly recommended to work with WhatsApp team closely when using these features so that we can support you quickly, if there are any issues.
WhatsApp Enterprise client doesn't work when HA is disabled. This will be addressed in next WhatsApp Enterprise Client release.