Bernhard B.

> @bbernhard it seems the issue is actually here: > > ```go > combinedOutput := stdoutBuffer.String() + stderrBuffer.String() > ``` > > [snip](https://github.com/bbernhard/signal-cli-rest-api/blob/master/src/client/cli.go#L142) > > all logs are printed to...

I think the info and warn messages are also important (as they are often an indication that something is not working as intended or is going to break in the...

> Yes, that would make sense, but it would also require to break the fix for #403 > > > I don't know the internals of signal-cli well enough, but...

> > Is the only problem that we don't escape a JSON injection? If so, couldn't we just do that? It should always be a good idea, not only for...

Thanks a lot!

As mentioned [here](https://github.com/AsamK/signal-cli/issues/1456) you get the information via the `receive`. The `receive` command is exposed via the `receive` REST API endpoint.

In json-rpc node you need to establish a websocket connection instead of a HTTP connection to the `receive` endpoint. You can use any websocket client you want. e.g `wscat`

> When my service which uses REST API isn't up for a long time, and then I try to receive messages, I get `{"error":"process killed as timeout reached"}` and messages...

If I understood you correctly, then the cli returned `Error while checking account : [401] Authorization failed!`, which isn't shown in the API response, right? Do you maybe can post...

The `/v1/send` endpoint is actually deprecated and replaced by `/v2/send` (see also the swagger documentation [here](https://bbernhard.github.io/signal-cli-rest-api/))