Unable to cross `url_verification` phase in Event Request URL setup

[sinchanroy]

Description

unable to cross url_verification phase in slack.

What type of issue is this? (place an x in one of the [ ])

• [x] bug
• [ ] enhancement (feature request)
• [ ] question
• [ ] documentation related
• [ ] testing related
• [ ] discussion

Requirements

• [x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
• [x] I've read and agree to the Code of Conduct.
• [x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report

Filling out the following details about bugs will help us solve your issue sooner.

Reproducible in:

slackeventsapi version: 3.0.1 python version: 3.8 OS version(s): Mac 13

Steps to reproduce:

Follow the steps as mentioned in Readme

Expected result:

App Events is verified in Slack

Actual result:

Our Request:
POST
"body": { 
     "type": "url_verification",
     "token": "",
     "challenge": ""
}
Your Response:
"code": 
"error": "challenge_failed"
"body": {

}

Attachments:

Logs, screenshots, screencast, sample project, funny gif, etc.

[srajiang]

Hi @sinchanroy - Can you please provide some more information about how your application is handling the inbound verification request from Slack? When you are setting up Event Request URL, your app must verify the validity of the request from Slack (using the Signing Secret available in your Apps App Config page) return a 200 OK and the value of the challenge.

Here's more information about handling the url_verification event: https://api.slack.com/events/url_verification

[seratch]

@sinchanroy If you're trying to configure the app with endpoint="/slack/events" like README does, you need to pass https://{domain}/slack/events instead.

[srajiang]

@sinchanroy Can you please give what @seratch suggested a try (adding /slack/events) to the end of your request URL domain in the Event Request URL UI, and let us know if that resolves your issue?

[github-actions[bot]]

👋 It looks like this issue has been open for 30 days with no activity. We'll mark this as stale for now, and wait 10 days for an update or for further comment before closing this issue out.

[github-actions[bot]]

As this issue has been inactive for more than one month, we will be closing it. Thank you to all the participants! If you would like to raise a related issue, please create a new issue which includes your specific details and references this issue number.