We are excited to announce the release of WAHA - 2023.12, which includes two months of work from the previous 2023.9 release!

You can find the full changelog here: WAHA Changelog

Send a video to your participant using WAHA - we added a new endpoint for that, POST /api/sendVideo!

It works on WEBJS and NOWEB engines (available in WAHA Plus version).

Send the URL or base64 encoded file to the POST /api/sendVideo

Session Status WebhookPreviously, WAHA had only "engine-specific" event for sessions - state.change. We added a new event - session.status, which you can use to get recent status updates from the session!

The session.status event is triggered when the session status changes.

- `STOPPED` - session is stopped

- `STARTING` - session is starting

- `SCAN_QR_CODE` - session is required to scan QR code or login via phone number

- `WORKING` - session is working and ready to use

- `FAILED` - session has failed due to some error. It’s likely that authorization is required again or the device has been disconnected from that account. Try to restart the session and if it doesn’t help - logout and start the session again.

Added a dedicated `media` field in the webhook payload - now you can know which media is attached to the message.

If you are interested only in text messages or messages with specific files, such as only images or PDF files, you can manage what type of media WAHA processes!

- `WHATSAPP_FILES_MIMETYPES`: This variable can be used to download only specific mimetypes from messages. By default, all files are downloaded. The mimetypes must be separated by a comma without spaces. For example, `audio,image/png,image/gif`. To choose a specific type, use a prefix (like `audio,image`). See usage below.

- `WHATSAPP_DOWNLOAD_MEDIA=true`: This variable can be used to completely disable downloading media files. By default, all files are downloaded. Set this variable to `WHATSAPP_DOWNLOAD_MEDIA=false` to disable downloading media files.

If you're concerned about exposing Swagger to the internet in production, you can completely hide the Swagger UI from your installation by setting the WHATSAPP_SWAGGER_ENABLED=false environment variable. Keep in mind that this does not protect your API. We recommend protecting your API with an API Key as well, even if you hide the Swagger UI or set a password for the Swagger UI.

By default, `GET /api/{session}/auth/qr` returns a binary QR code image. You can change that behavior in two ways and get the QR code in different formats:

1. Binary Image - `GET /api/{session}/auth/qr`- default format, you’ll get an image in response.

2. Base64 Image - `GET /api/{session}/auth/qr` and set the `Accept: application/json` header - you’ll get the image in base64 format in response.

3. **Raw** - `GET /api/{session}/auth/qr? format=raw`, you’ll get raw data in response, which you can use to generate the QR code on your side.

You can get a screenshot in base64 format by adding the `Accept: application/json` header to the request.

We're glad you're using and supporting the project! Without your support, we wouldn't be able to continue working on the project!