http://localhost:8080/v1/send<recipient number> leads to 404 Page Not Found

[oleua]

The problem

Hi! I am trying to use the dockerised service together with the Nextcloud two-factor gateway app.

It doesn't work and in the log I see error 404 Page Not Found

GuzzleHttp\Exception\ClientException: Client error: POST http://127.0.0.1:8080/v1/send/`

resulted in a response: 404 page not found

I have inspected the code and found that it uses v1 in sending messages. I've tried manual command in the shell curl -d '{"message": "foo"}' http://127.0.0.1:8080/v1/send/<recipient_number> and got the same response: 404 page not found.

Doesn't your signal API implementation support v1 at all?

Are you using the latest released version?

• [X] Yes

Have you read the troubleshooting page?

• [X] Yes

What type of installation are you running?

signal-cli-rest-api Docker Container

In which mode are you using the docker container?

Normal Mode

What's the architecture of your host system?

x86-64

Additional information

No response

[bbernhard]

The /v1/send endpoint is actually deprecated and replaced by /v2/send (see also the swagger documentation here)

[oleua]

The /v1/send endpoint is actually deprecated and replaced by /v2/send (see also the swagger documentation here)

I see... Is it possible to add the compatibility layer? As in my case your service implementation is not workable (

[oleua]

Would that be possible to pass the SIGNAL_CLI_DBUS_REST_API_ACCOUNT as the default number of the account when sending messages as a value of number?

Or with a special command to get the registered number?

[bbernhard]

What do you mean with SIGNAL_CLI_DBUS_REST_API_ACCOUNT?

[oleua]

What do you mean with SIGNAL_CLI_DBUS_REST_API_ACCOUNT?

The registered phone number or account name.