Seems the token was missing from the request.

[aubelsb2]

As far as I can tell it's because of a token is missing.

[aubelsb2]

Probably handled in the http client.

[aubelsb2]

Verified to fix my issue. Seems they are checking for unnecessary parameters or at least token being in the wrong location.

[kanata2]

@aubelsb2

I commented related issue. #903 (comment)
Could you fix other codes where same problems occur too?(if exists)
If it is difficult, please let me know so I can find the time to do it.

[bailantaotao]

Is there any update for this?

[aubelsb2]

When I get a weekend spare I can work on it.

[raylas]

Would also love to see this merged ☝🏼

[joshm91]

Looks like #921 fixes this issue properly. This library is pretty much broken to any newcomers at the moment so it'd be great to get the fix merged ASAP. Thanks!

[kanata2]

Relased in v0.8.3

[arran4]

Following up from personal account. Does effort still need to be done by me? I feel like the change to remove query param token from the library will require significant change.

[kanata2]

In my recognition, #857 was resolved in v0.8.3.

However it may be better to use application/json as Slack's recommendation(the followings).

Some methods, like chat.postMessage and dialog.open feature arguments that accept an associative JSON array. These methods can be difficult to properly construct when using a application/x-www-form-urlencoded Content-type, and we strongly recommend using JSON-encoded bodies instead.