-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What token is required to use the RTM client? #250
Comments
I think there are several types allowed. At another place I don't have admin, so I cannot check. Does anyone know? |
The docs for https://api.slack.com/methods/rtm.connect say name two options: So the Legacy bot token is probably my usage. Then the other answer is "User token" which I have little experience with. |
Would you be open to adding a socket mode client to this library? |
That'd be a great contribution. Feel free to proceed. Please consult if you want to add new non trivial dependencies. Which I guess is likely for sockets. |
Thanks. My understanding is the RTM client starts a websocket connection with slack. If so, the SocketMode client would do something very similar. It actually also requires a websocket connection, not just a normal socket connection. |
From various tutorials, it seems that the current bot setup supported by slack is to create an app and a bot, each of which have a token. The
SlackRtmClient
, and I've tried both my bot and app token and neither seem to work.I end up with
Exception in thread "main" slack.api.ApiError: not_allowed_token_type
The text was updated successfully, but these errors were encountered: