Version 0.58

• updated signal-cli to version 0.10.4.2
• added API endpoints to add/remove admins to/from Signal Groups
• added API endpoints to add/remove members to/from Signal Groups
• added API endpoint to add a device
• added API endpoint to update a contact

Version 0.57

• updated signal-cli to v0.10.4.1
• linked devices can now be used in json-rpc mode
• made swagger IP address configurable. Per default the container IP address will be used as swagger IP. If a different IP address should be used, set the SWAGGER_IP env variable in the docker-compose.yml
• improved documentation (thanks to @jarrah31)

Version 0.56

• updated signal-cli to version 0.10.4
• improved & updated documentation (thanks to @bentolor and @stilsch)
• reduced docker container size (thanks to @bentolor)
• made uid and gid inside docker container configurable
• fixed bug in update profile REST API request (due to a bug it wasn't possible anymore to set the avatar)

Version 0.55

• updated signal-cli to version 0.10.0 (uses now Java 17)
• improved qrcodelink endpoint (generate QR code with version 10 and the highest error correction level)
• added search endpoint (allows to check whether a phone number is registered with the signal service)
• added unregister endpoint
• fixed bug in json-rpc mode (properly close websocket connection when client disconnects)

Info: Due to this GraalVM issue I can't build the arm64 native signal-cli myself anymore. So, beginning with this release, the signal-cli native binary from @morph027 (https://gitlab.com/packaging/signal-cli) will be used for arm64. Many thanks to @morph027

Version 0.55

• updated signal-cli to v0.10.0

WARNING

Due to this issue here, this release won't contain a native image for arm64. So, if you are using MODE: native on arm64, either switch to the ´json-rpc` mode (recommended) or don't update for now.

This is a pre-release. In case you want to give it a try, please use this image tag: bbernhard/signal-cli-rest-api:0.85-dev

Version 0.54

• fixed excessive logging
• fixed bug in list groups endpoint

Version 0.53

• do not hardcode path to signal-cli config directory inside the docker container
• added endpoints for adding/deleting reactions (thanks to @filipre)
• fixed swagger documentation: for several endpoints the HTTP status code was incorrect in the swagger documentation
• fixed bug in JSON-RPC mode: block group wasn't working
• improved/extended Home Assistant documentation (thanks to @akloeckner)

Version 0.52

• updated signal-cli to version 0.9.2
• added new endpoint to show/hide typing indicator

Version 0.51

• return mode (normal, native, json-rpc) in about endpoint
• fixed bug in create group endpoint: the group id of the newly created signal group wasn't correctly returned in json-rpc mode.

Version 0.50

Features

This release makes the JSON-RPC mode (which was released with signal-cli v0.9.0) available in the signal-cli-rest-api.

For implementation details, discussions and troubleshooting see: #160

Limitations, API changes & Breaking Changes:

• Registering, verifying and linking devices only works in normal/native mode. (there's no support yet in signal-cli)
• In JSON-RPC mode it's no longer possible to poll for incoming messages via the HTTP GET receive endpoint. Instead you have to use websockets. e.g: In order to listen for incoming messages you can use wscat like this: wscat -c 127.0.0.1:8080/v1/receive/<your registered signal number> --show-ping-pong --slash
• The USE_NATIVE env variable in the docker-compose.yml file is now deprecated. You can still use it, but you'll see a deprecation warning in the logs. It is recommended to use the MODE env variable instead. (e.g: MODE=native)
• The AUTO_RECEIVE_SCHEDULE env variable in the docker-compose.yml only works in normal/native mode
• The SIGNAL_CLI_CMD_TIMEOUT env variable in the docker-compose.yml only works in normal/native mode