docs: replace links from api.slack.com to docs.slack.dev redirects

Author: zimeg

.github/ISSUE_TEMPLATE/03_document.md

@@ -10,7 +10,7 @@ assignees: ''
 
 ### The page URLs
 
-* https://slack.dev/bolt-python/
+* https://docs.slack.dev/tools/bolt-python/
 
 ## Requirements
 

README.md

@@ -60,7 +60,7 @@ ngrok http 3000
 
 ## Running a Socket Mode app
 
-If you use [Socket Mode](https://api.slack.com/socket-mode) for running your app, `SocketModeHandler` is available for it.
+If you use [Socket Mode](https://docs.slack.dev/apis/events-api/using-socket-mode/) for running your app, `SocketModeHandler` is available for it.
 
 ```python
 import os
@@ -91,7 +91,7 @@ python app.py
 
 ## Listening for events
 
-Apps typically react to a collection of incoming events, which can correspond to [Events API events](https://api.slack.com/events-api), [actions](https://api.slack.com/interactivity/components), [shortcuts](https://api.slack.com/interactivity/shortcuts), [slash commands](https://api.slack.com/interactivity/slash-commands) or [options requests](https://api.slack.com/reference/block-kit/block-elements#external_select). For each type of
+Apps typically react to a collection of incoming events, which can correspond to [Events API events](https://docs.slack.dev/apis/events-api/), [actions](https://docs.slack.dev/block-kit/#making-things-interactive), [shortcuts](https://docs.slack.dev/interactivity/implementing-shortcuts/), [slash commands](https://docs.slack.dev/interactivity/implementing-slash-commands/) or [options requests](https://docs.slack.dev/reference/block-kit/block-elements/select-menu-element#external_select). For each type of
 request, there's a method to build a listener function.
 
 ```python
@@ -138,12 +138,12 @@ Most of the app's functionality will be inside listener functions (the `fn` para
 | Argument  | Description  |
 | :---: | :--- |
 | `body` | Dictionary that contains the entire body of the request (superset of `payload`). Some accessory data is only available outside of the payload (such as `trigger_id` and `authorizations`).
-| `payload` | Contents of the incoming event. The payload structure depends on the listener. For example, for an Events API event, `payload` will be the [event type structure](https://api.slack.com/events-api#event_type_structure). For a block action, it will be the action from within the `actions` list. The `payload` dictionary is also accessible via the alias corresponding to the listener (`message`, `event`, `action`, `shortcut`, `view`, `command`, or `options`). For example, if you were building a `message()` listener, you could use the `payload` and `message` arguments interchangably. **An easy way to understand what's in a payload is to log it**. |
+| `payload` | Contents of the incoming event. The payload structure depends on the listener. For example, for an Events API event, `payload` will be the [event type structure](https://docs.slack.dev/apis/events-api/#event-type-structure). For a block action, it will be the action from within the `actions` list. The `payload` dictionary is also accessible via the alias corresponding to the listener (`message`, `event`, `action`, `shortcut`, `view`, `command`, or `options`). For example, if you were building a `message()` listener, you could use the `payload` and `message` arguments interchangably. **An easy way to understand what's in a payload is to log it**. |
 | `context` | Event context. This dictionary contains data about the event and app, such as the `botId`. Middleware can add additional context before the event is passed to listeners.
-| `ack` | Function that **must** be called to acknowledge that your app received the incoming event. `ack` exists for all actions, shortcuts, view submissions, slash command and options requests. `ack` returns a promise that resolves when complete. Read more in [Acknowledging events](https://tools.slack.dev/bolt-python/concepts/acknowledge).
+| `ack` | Function that **must** be called to acknowledge that your app received the incoming event. `ack` exists for all actions, shortcuts, view submissions, slash command and options requests. `ack` returns a promise that resolves when complete. Read more in [Acknowledging events](https://docs.slack.dev/tools/bolt-python/concepts/acknowledge/).
 | `respond` | Utility function that responds to incoming events **if** it contains a `response_url` (shortcuts, actions, and slash commands).
 | `say` | Utility function to send a message to the channel associated with the incoming event. This argument is only available when the listener is triggered for events that contain a `channel_id` (the most common being `message` events). `say` accepts simple strings (for plain-text messages) and dictionaries (for messages containing blocks).
-| `client` | Web API client that uses the token associated with the event. For single-workspace installations, the token is provided to the constructor. For multi-workspace installations, the token is returned by using [the OAuth library](https://tools.slack.dev/bolt-python/concepts/authenticating-oauth), or manually using the `authorize` function.
+| `client` | Web API client that uses the token associated with the event. For single-workspace installations, the token is provided to the constructor. For multi-workspace installations, the token is returned by using [the OAuth library](https://docs.slack.dev/tools/bolt-python/concepts/authenticating-oauth/), or manually using the `authorize` function.
 | `logger` | The built-in [`logging.Logger`](https://docs.python.org/3/library/logging.html) instance you can use in middleware/listeners.
 | `complete` | Utility function used to signal the successful completion of a custom step execution. This tells Slack to proceed with the next steps in the workflow. This argument is only available with the `.function` and `.action` listener when handling custom workflow step executions.
 | `fail` | Utility function used to signal that a custom step failed to complete. This tells Slack to stop the workflow execution. This argument is only available with the `.function` and `.action` listener when handling custom workflow step executions.
@@ -192,7 +192,7 @@ Apps can be run the same way as the syncronous example above. If you'd prefer an
 
 ## Getting Help
 
-[The documentation](https://tools.slack.dev/bolt-python) has more information on basic and advanced concepts for Bolt for Python. Also, all the Python module documents of this library are available [here](https://tools.slack.dev/bolt-python/reference/).
+[The documentation](https://docs.slack.dev/tools/bolt-python/) has more information on basic and advanced concepts for Bolt for Python. Also, all the Python module documents of this library are available [here](https://docs.slack.dev/tools/bolt-python/reference/).
 
 If you otherwise get stuck, we're here to help. The following are the best ways to get assistance working through your issue:
 

docs/english/tutorial/custom-steps-workflow-builder-existing/custom-steps-workflow-builder-existing.md

@@ -9,7 +9,7 @@ If you followed along with our [create a custom step for Workflow Builder: new a
 In this tutorial we will:
 - Start with an existing Bolt app
 - Add a custom **workflow step** in the [app settings](https://api.slack.com/apps)
-- Wire up the new step to a **function listener** in our project, using the [Bolt for Python](https://slack.dev/bolt-python/) framework
+- Wire up the new step to a **function listener** in our project, using the [Bolt for Python](https://docs.slack.dev/tools/bolt-python/) framework
 - See the step as a custom workflow step in Workflow Builder
 
 ## Prerequisites {#prereqs}

examples/aws_lambda/README.md

@@ -32,16 +32,16 @@ Instructions on how to set up and deploy each example are provided below.
       `lazy_aws_lambda_config.yaml`
   - Optionally enter a description for the role, such as "Bolt Python basic
       role"
-3. Ensure you have created an app on api.slack.com/apps as per the [Getting
-   Started Guide](https://slack.dev/bolt-python/tutorial/getting-started).
+3. Ensure you have created an app on api.slack.com/apps as per the
+   [Building an App](https://docs.slack.dev/tools/bolt-python/building-an-app) guide.
    Ensure you have installed it to a workspace.
 4. Ensure you have exported your Slack Bot Token and Slack Signing Secret for your
    apps as the environment variables `SLACK_BOT_TOKEN` and
-   `SLACK_SIGNING_SECRET`, respectively, as per the [Getting
-   Started Guide](https://slack.dev/bolt-python/tutorial/getting-started).
+   `SLACK_SIGNING_SECRET`, respectively, as per the
+   [Building an App](https://docs.slack.dev/tools/bolt-python/building-an-app) guide.
 5. You may want to create a dedicated virtual environment for this example app, as
-   per the "Setting up your project" section of the [Getting
-   Started Guide](https://slack.dev/bolt-python/tutorial/getting-started).
+   per the "Setting up your project" section of the
+   [Building an App](https://docs.slack.dev/tools/bolt-python/building-an-app) guide.
 6. Let's deploy the Lambda! Run `./deploy_lazy.sh`. By default it deploys to the
    us-east-1 region in AWS - you can change this at the top of `lazy_aws_lambda_config.yaml` if you wish.
 7. Load up AWS Lambda inside the AWS Console - make sure you are in the correct
@@ -150,7 +150,7 @@ Let’s create a user role that will use the custom policy we created as well as
     3. "Create Role"
 
 ### Create Slack App and Load your Lambda to AWS
-Ensure you have created an app on [api.slack.com/apps](https://api.slack.com/apps) as per the [Getting Started Guide](https://slack.dev/bolt-python/tutorial/getting-started). You do not need to ensure you have installed it to a workspace, as the OAuth flow will provide your app the ability to be installed by anyone.
+Ensure you have created an app on [api.slack.com/apps](https://api.slack.com/apps) as per the [Building an App](https://docs.slack.dev/tools/bolt-python/building-an-app) guide. You do not need to ensure you have installed it to a workspace, as the OAuth flow will provide your app the ability to be installed by anyone.
 
 1. Remember those S3 buckets we made? You will need the names of these buckets again in the next step.
 2. You need many environment variables exported! Specifically the following from api.slack.com/apps

examples/django/README.md

@@ -4,7 +4,7 @@ This example demonstrates how you can use Bolt for Python in your Django applica
 
 ### `simple_app` - Single-workspace App Example
 
-If you want to run a simple app like the one you've tried in the [Getting Started Guide](https://slack.dev/bolt-python/tutorial/getting-started), this is the right one for you. By default, this Django project runs this application. If you want to switch to OAuth flow supported one, modify `myslackapp/urls.py`.
+If you want to run a simple app like the one you've tried in the [Building an App](https://docs.slack.dev/tools/bolt-python/building-an-app) guide, this is the right one for you. By default, this Django project runs this application. If you want to switch to OAuth flow supported one, modify `myslackapp/urls.py`.
 
 To run this app, all you need to do are:
 
@@ -31,7 +31,7 @@ python manage.py migrate
 python manage.py runserver 0.0.0.0:3000
 ```
 
-As you did at [Getting Started Guide](https://slack.dev/bolt-python/tutorial/getting-started), configure ngrok or something similar to serve a public endpoint. Lastly,
+As you did at [Building an App](https://docs.slack.dev/tools/bolt-python/building-an-app) guide, configure ngrok or something similar to serve a public endpoint. Lastly,
 
 * Go back to the Slack app configuration page
 * Go to "Event Subscriptions"
@@ -54,7 +54,7 @@ To run this app, all you need to do are:
 * Create a new Slack app configuration at https://api.slack.com/apps?new_app=1
 * Go to "OAuth & Permissions"
   * Add `app_mentions:read`, `chat:write` in Scopes > Bot Token Scopes
-* Follow the instructions [here](https://slack.dev/bolt-python/concepts#authenticating-oauth) for configuring OAuth flow supported Slack apps
+* Follow the instructions [here](https://docs.slack.dev/tools/bolt-python/concepts/authenticating-oauth) for configuring OAuth flow supported Slack apps
 
 You can start your Django application this way:
 
@@ -73,7 +73,7 @@ python manage.py migrate
 python manage.py runserver 0.0.0.0:3000
 ```
 
-As you did at [Getting Started Guide](https://slack.dev/bolt-python/tutorial/getting-started), configure ngrok or something similar to serve a public endpoint. Lastly,
+As you did at [Building an App](https://docs.slack.dev/tools/bolt-python/building-an-app) guide, configure ngrok or something similar to serve a public endpoint. Lastly,
 
 * Go back to the Slack app configuration page
 * Go to "Event Subscriptions"

examples/getting_started/README.md

@@ -1,5 +1,5 @@
 # Getting Started with ⚡️ Bolt for Python
-> Slack app example from 📚 [Getting started with Bolt for Python][1]
+> Slack app example from 📚 [Building an App with Bolt for Python][1]
 
 ## Overview
 
@@ -42,6 +42,6 @@ ngrok http 3000
 python3 app.py
 ```
 
-[1]: https://slack.dev/bolt-python/tutorial/getting-started
-[2]: https://slack.dev/bolt-python/
-[3]: https://slack.dev/bolt-python/tutorial/getting-started#setting-up-events
+[1]: https://docs.slack.dev/tools/bolt-python/building-an-app
+[2]: https://docs.slack.dev/tools/bolt-python/
+[3]: https://docs.slack.dev/tools/bolt-python/building-an-app#setting-up-events

examples/message_events.py

@@ -32,7 +32,7 @@ def extract_subtype(body: dict, context: BoltContext, next: Callable):
     next()
 
 
-# https://api.slack.com/events/message
+# https://docs.slack.dev/reference/events/message/
 # Newly posted messages only
 # or @app.event("message")
 @app.event({"type": "message", "subtype": None})
@@ -55,8 +55,8 @@ def detect_deletion(say: Say, body: dict):
     say(f"You've deleted a message: {text}")
 
 
-# https://api.slack.com/events/message/file_share
-# https://api.slack.com/events/message/bot_message
+# https://docs.slack.dev/reference/events/message/file_share
+# https://docs.slack.dev/reference/events/message/bot_message
 @app.event(
     event={"type": "message", "subtype": re.compile("(me_message)|(file_share)")},
     middleware=[extract_subtype],

examples/readme_app.py

@@ -16,13 +16,13 @@ def log_request(logger, body, next):
     return next()
 
 
-# Events API: https://api.slack.com/events-api
+# Events API: https://docs.slack.dev/apis/events-api/
 @app.event("app_mention")
 def event_test(say):
     say("What's up?")
 
 
-# Interactivity: https://api.slack.com/interactivity
+# Interactivity: https://docs.slack.dev/interactivity/
 @app.shortcut("callback-id-here")
 # @app.command("/hello-bolt-python")
 def open_modal(ack, client, logger, body):

examples/readme_async_app.py

@@ -28,13 +28,13 @@ async def log_request(logger, body, next):
     return await next()
 
 
-# Events API: https://api.slack.com/events-api
+# Events API: https://docs.slack.dev/apis/events-api/
 @app.event("app_mention")
 async def event_test(say):
     await say("What's up?")
 
 
-# Interactivity: https://api.slack.com/interactivity
+# Interactivity: https://docs.slack.dev/interactivity/
 @app.shortcut("callback-id-here")
 # @app.command("/hello-bolt-python")
 async def open_modal(ack, client, logger, body):

examples/workflow_steps/async_steps_from_apps.py

@@ -11,7 +11,7 @@
 
 ################################################################################
 # Steps from apps for legacy workflows are now deprecated.                     #
-# Use new custom steps: https://api.slack.com/automation/functions/custom-bolt #
+# Use new custom steps: https://docs.slack.dev/workflows/workflow-steps/       #
 ################################################################################
 
 logging.basicConfig(level=logging.DEBUG)