Updated from Slack docs, 2026/02/11

Author: Slack API Ref Buildbot

docs.slack.dev/methods/admin.conversations.unlinkObjects.json

@@ -3,7 +3,7 @@
   "http_method": "POST",
   "scope": {
     "user": [
-      "admin.conversations:write"
+      "admin.conversations:manage_objects"
     ]
   },
   "json_input_supported": true,

docs.slack.dev/methods/chat.appendStream.json

@@ -32,6 +32,10 @@
         "type": "string",
         "subtype": "channel"
       },
+      "chunks": {
+        "desc": "An array of streaming chunks. Chunks can be markdown text chunks, task update chunks, and plan update chunks.",
+        "type": "array"
+      },
       "ts": {
         "desc": "The timestamp of the streaming message.",
         "schema": "ts"

docs.slack.dev/methods/chat.startStream.json

@@ -31,6 +31,10 @@
         "type": "string",
         "subtype": "channel"
       },
+      "chunks": {
+        "desc": "An array of streaming chunks. Chunks can be markdown text chunks, task update chunks, and plan update chunks.",
+        "type": "array"
+      },
       "markdown_text": {
         "desc": "Accepts message text formatted in markdown. Limit this field to 12,000 characters.",
         "type": "string",
@@ -50,6 +54,16 @@
         "desc": "The encoded ID of the team the user receiving the streaming text belongs to. Required when streaming to channels.",
         "type": "string",
         "example": "T0123456789"
+      },
+      "task_display_mode": {
+        "desc": "Specifies how tasks are displayed in the message. A `timeline` displays individual tasks with text in sequential order, and `plan` displays all tasks together, with the first tasks's placement determining the placement of the rest of the tasks.",
+        "type": "string",
+        "enum": [
+          "timeline",
+          "plan"
+        ],
+        "default": "timeline",
+        "example": "plan"
       }
     }
   },

docs.slack.dev/methods/chat.stopStream.json

@@ -31,6 +31,10 @@
         "type": "string",
         "subtype": "channel"
       },
+      "chunks": {
+        "desc": "An array of streaming chunks. Chunks can be markdown text chunks, task update chunks, and plan update chunks.",
+        "type": "array"
+      },
       "ts": {
         "desc": "The timestamp of the streaming message.",
         "schema": "ts"

methods/chat/chat.appendStream.json

@@ -9,6 +9,11 @@
       "desc": "An encoded ID that represents a channel, private group, or DM.",
       "type": "channel"
     },
+    "chunks": {
+      "required": false,
+      "desc": "An array of streaming chunks. Chunks can be markdown text chunks, task update chunks, and plan update chunks.",
+      "type": "array"
+    },
     "ts": {
       "required": true,
       "desc": "The timestamp of the streaming message.",

methods/chat/chat.startStream.json

@@ -9,6 +9,11 @@
       "desc": "An encoded ID that represents a channel thread or DM.",
       "type": "channel"
     },
+    "chunks": {
+      "required": false,
+      "desc": "An array of streaming chunks. Chunks can be markdown text chunks, task update chunks, and plan update chunks.",
+      "type": "array"
+    },
     "markdown_text": {
       "required": false,
       "example": "**This is bold text**",
@@ -30,6 +35,12 @@
       "example": "T0123456789",
       "desc": "The encoded ID of the team the user receiving the streaming text belongs to. Required when streaming to channels.",
       "type": "string"
+    },
+    "task_display_mode": {
+      "required": false,
+      "example": "plan",
+      "desc": "Specifies how tasks are displayed in the message. A timeline displays individual tasks with text in sequential order, and plan displays all tasks together, with the first tasks's placement determining the placement of the rest of the tasks.",
+      "type": "enum"
     }
   },
   "response": {

methods/chat/chat.stopStream.json

@@ -9,6 +9,11 @@
       "desc": "An encoded ID that represents a channel, private group, or DM.",
       "type": "channel"
     },
+    "chunks": {
+      "required": false,
+      "desc": "An array of streaming chunks. Chunks can be markdown text chunks, task update chunks, and plan update chunks.",
+      "type": "array"
+    },
     "ts": {
       "required": true,
       "desc": "The timestamp of the streaming message.",