Rohit Singh

Thank You for your reply. Here is what I tried. I created a app and added some permission to it. Then I installed the app in a workspace. This game...

Yes you are correct { "ok": false, "error": "not_allowed_token_type" } Since I do not have legacy token. May be using this method to connect is not possible with new token.

Yep I see the same 404 To experiment I added following to user scope and user scope token  Then I get { "ok": false, "error": "missing_scope", "needed": "rtm:stream", "provided":...

The page is working now. You can always read it from google cache https://webcache.googleusercontent.com/search?q=cache:Z9rojI6BWjEJ:https://api.slack.com/events-api+&cd=1&hl=en&ct=clnk&gl=us&client=ubuntu Yes classic app are still there. However they do not let you create new legacy tokens....

TY I created a classic slack app. I got bot token from there and I tried the example again. It did not work. first the URL this time looks valid...

TY for patience and help. I tried running directly from clone. still same  only reference that I can find for "scheme is not http" is from hyper. hyper does...

Thank You it does work now with your update. I think we can update the document to state 1. create a classic app 2. get bot token from oauth that...

@owennewo your suggestion does solve the problem. This is proper work around thank you.