feat(docs): update bot related APIs

Author: oliwiapolec

src/pages/management/configuration-api/index.mdx

@@ -1515,6 +1515,7 @@ Updates an existing Bot.
 | `groups[].id`                            | Yes      | `uint`     | Group ID, required only when `groups`'s present.                                                  |
 | `groups[].priority`<sup>**1**</sup>      | Yes      | `string`   | Bot's priority in the group; required only when `groups` is included.                             |
 | `default_group_priority`<sup>**1**</sup> | No       | `string`   | The default routing priority for a group without defined priority.                                |
+| `job_title`                              | No       | `string`   | Bot's job title                                                                                   |
 | `work_scheduler`                         | No       | `object`   | Work scheduler options to set for the new Bot. See [**Create Agent**](#create-agent) for details. |
 | `work_scheduler.timezone`                | Yes      | `string`   | The time zone in which the Bot's work scheduler should operate.                                   |
 

src/pages/management/configuration-api/v3.6/index.mdx

@@ -1499,6 +1499,7 @@ Updates an existing bot.
 | `groups[].id`                            | Yes      | `uint`     | Group ID, required only when `groups`'s present.                                                  |
 | `groups[].priority`<sup>**1**</sup>      | Yes      | `string`   | Bot's priority in the group; required only when `groups` is included.                             |
 | `default_group_priority`<sup>**1**</sup> | No       | `string`   | The default routing priority for a group without defined priority.                                |
+| `job_title`                              | No       | `string`   | Bot's job title                                                                                   |
 | `work_scheduler`                         | No       | `object`   | Work scheduler options to set for the new bot. See [**Create Agent**](#create-agent) for details. |
 | `work_scheduler.timezone`                | Yes      | `string`   | The time zone in which the bot's work scheduler should operate.                                   |
 

src/pages/messaging/agent-chat-api/rtm-reference/index.mdx

@@ -82,12 +82,9 @@ The `filters`, `limit`, and `sort_order` parameters can't be provided along with
 
 💡 The maximum duration of the `page_id` parameter before it expires is one month.
 
-## Calling the API as a bot
+## Calling the RTM API as a bot
 
-It's possible to call the Agent Chat API as a bot. There are two ways to authorize the requests:
-
-- old (v3.5 and lower): a bot shares the access token with the agent who created it. You need to provide the [agent token](/authorization/agent-authorization/) (Bearer or Basic Auth) and the `X-Author-Id: <bot_id>` header in the request.
-- new (v3.5 and higher): bots use their own authorization tokens generated with the [Issue Bot Token](/management/configuration-api/v3.5/#issue-bot-token) method.
+Establishing a WebSocket connection as a bot is currently unsupported. If you want to call the Agent Chat API as a bot, you should use the [Web API](/messaging/agent-chat-api#calling-the-api-as-a-bot) instead.
 
 # Data structures
 

src/pages/messaging/agent-chat-api/v3.4/rtm-reference/index.mdx

@@ -89,11 +89,7 @@ The `filters`, `limit`, and `sort_order` parameters can't be provided along with
 
 ## Calling the API as a bot
 
-Sometimes, you want to [send an event as a bot](#send-event). To do it, you need to have a token that allows you to send it. The token can be easily generated for an agent, but you cannot generate a token for a bot. The other time you want to [add a user to your chat](#add-user-to-chat), and this user happens to be a bot in the group with no access to this chat, so you cannot add it.  
-
-In both situations, the `Author-Id` header is what you need to include in your request. With it, you can authorize using the agent’s token and send the event as a bot or add a bot to a chat even if the bot belongs to the group that has no access to this chat.
-
-`Author-Id: <bot_id>` header is needed with a [Bearer Token](/authorization/agent-authorization/) that needs to have the same `client_id` as the bot or [PAT](/authorization/agent-authorization#personal-access-tokens) that is from the organization that owns the bot's `client_id`.
+Establishing a WebSocket connection as a bot is currently unsupported. If you want to call the Agent Chat API as a bot, you should use the [Web API](/messaging/agent-chat-api#calling-the-api-as-a-bot) instead.
 
 # Data structures
 

src/pages/messaging/agent-chat-api/v3.6/rtm-reference/index.mdx

@@ -83,13 +83,9 @@ The `filters`, `limit`, and `sort_order` parameters can't be provided along with
 
 💡 The maximum duration of the `page_id` parameter before it expires is one month.
 
-## Calling the API as a bot
+## Calling the RTM API as a bot
 
-Sometimes, you want to [send an event as a bot](#send-event). To do it, you need to have a token that allows you to send it. The token can be easily generated for an agent, but you cannot generate a token for a bot. The other time you want to [add a user to your chat](#add-user-to-chat), and this user happens to be a bot in the group with no access to this chat, so you cannot add it.
-
-In both situations, the `Author-Id` header is what you need to include in your request. With it, you can authorize using the agent’s token and send the event as a bot or add a bot to a chat even if the bot belongs to the group that has no access to this chat.
-
-`Author-Id: <bot_id>` header is needed with a [Bearer Token](/authorization/agent-authorization/) that needs to have the same `client_id` as the bot or [PAT](/authorization/agent-authorization#personal-access-tokens) that is from the organization that owns the bot's `client_id`.
+Establishing a WebSocket connection as a bot is currently unsupported. If you want to call the Agent Chat API as a bot, you should use the [Web API](/messaging/agent-chat-api#calling-the-api-as-a-bot) instead.
 
 # Data structures