Clarify request URL endpoints

README.md

@@ -27,6 +27,8 @@ const app = new App({
 })();
 ```
 
+> ⚙️ By default, Bolt will listen to the `/slack/events` endpoint of your public URL for all incoming requests (whether shortcuts, events, or interactivity payloads). When configuring Request URLs in your app configuration, the should all have `/slack/events` appended by default. You can modify the default behavior by passing an array of `endpoints` of type string into the constructor.
+
 ## Listening for events
 
 Apps typically react to incoming events, which can be events, actions, commands, or options requests. For each type of

docs/_basic/listening_responding_commands.md

@@ -11,6 +11,8 @@ Your app can use the `command()` method to listen to incoming slash command even
 Commands must be acknowledged with `ack()` to inform Slack your app has received the event.
 
 There are two ways to respond to slash commands. The first way is to use `say()`, which accepts a string or JSON payload. The second is `respond()` which is a utility for the `response_url`. These are explained in more depth in the [responding to actions](#action-respond) section.
+
+When configuring commands within your app configuration, you'll continue to append `/slack/events` to your request URL.
 </div>
 
 ```javascript

docs/_basic/listening_responding_shortcuts.md

@@ -15,6 +15,8 @@ Shortcuts must be acknowledged with `ack()` to inform Slack that your app has re
 
 Shortcuts include a `trigger_id` which an app can use to [open a modal](#creating-modals) that confirms the action the user is taking. 
 
+When configuring shortcuts within your app configuration, you'll continue to append `/slack/events` to your request URL.
+
 ⚠️ Note that global shortcuts do **not** include a channel ID. If your app needs access to a channel ID, you may use a [`conversations_select`](https://api.slack.com/reference/block-kit/block-elements#conversation_select) element within a modal. Message shortcuts do include channel ID.
 
 </div>

docs/_tutorials/getting_started.md

@@ -145,6 +145,8 @@ The output should show a generated URL that you can use (we recommend the one th
 
 Now you have a public-facing URL for your app that tunnels to your local machine. The Request URL that you use in your app configuration is composed of your public-facing URL combined with the URL your app is listening on. By default, Bolt apps listen at `/slack/events` so our full request URL would be `https://8e8ec2d7.ngrok.io/slack/events`.
 
+> ⚙️Bolt uses the `/slack/events` endpoint to listen to all incoming requests (whether shortcuts, events, or interactivity payloads). When configuring endpoints within your app configuration, you'll append `/slack/events` to all request URLs.
+
 Under the **Enable Events** switch in the **Request URL** box, go ahead and paste in your URL. As long as your Bolt app is still running, your URL should become verified.
 
 After your request URL is verified, scroll down to **Subscribe to Bot Events**. There are four events related to messages: `message.channels` (listens for messages in public channels), `message.groups` (listens for messages in private channels), `message.im` (listens for messages in the App Home/DM space), and `message.mpim` (listens for messages in multi-person DMs).