Change how messages are treated. Defaults to client, unlike chat.postMessage. See below.
Find and link channel names and usernames. Defaults to none. This parameter should be used in conjunction with parse. To set link_names to 1, specify a parse mode of full.
Pass true to update the message as the authed user. Bot users in this context are considered authed users.
The default value for parse will attempt to discover links in text but does not support URL markup. To update messages with URL markup, you must specify parse=none. For more information, refer to the formatting spec.
To use link_names, you'll need to explicitly set the parse parameter to full.
The optional attachments argument should contain a JSON-encoded array of attachments. If you do not include an attachments property,
a message's previous attachments will remain visible. To remove a previous attachment, include an empty attachments array with your request. For more information, see the attachments spec.
Valid message types
Only messages posted by the authenticated user are able to be updated using this method. This includes regular chat messages, as well as messages containing the me_message subtype. Bot users may also update the messages they post.
Attempting to update other message types will return a cant_update_message error.
The response includes the text, channel and timestamp properties of the
updated message so clients can keep their local copies of the message in sync.
To use chat.update with a bot user token, you'll need to think of your bot user as a user, and pass as_user set to true while editing a message created by that same bot user.
Interactive messages with buttons
If you're posting message with buttons, you may use chat.update to continue updating ongoing state changes around a message. Provide the ts field the message you're updating and follow the bot user instructions above to update message text, remove or add attachments and actions.
This table lists the expected errors that this method could return.
However, other errors can be returned in the case where the service is down
or other unexpected factors affect processing. Callers should always
check the value of the ok params in the response.
No message exists with the requested timestamp.
Authenticated user does not have permission to update this message.
Value passed for channel was invalid.
The message cannot be edited due to the team message edit settings
Message text is too long
Too many attachments were provided with this message. A maximum of 100 attachments are allowed on a message.
No message text provided
No authentication token provided.
Invalid authentication token.
Authentication token is for a deleted user or team.
The method was passed an argument whose name falls outside the bounds of common decency. This includes very long names and names with non-alphanumeric characters other than _. If you get this error, it is typically an indication that you have made a very malformed API call.
The method was passed a PHP-style array argument (e.g. with a name like foo). These are never valid with the Slack API.
The method was called via a POST request, but the charset specified in the Content-Type header was invalid. Valid charset names are: utf-8iso-8859-1.
The method was called via a POST request with Content-Typeapplication/x-www-form-urlencoded or multipart/form-data, but the form data was either missing or syntactically invalid.
The method was called via a POST request, but the specified Content-Type was invalid. Valid types are: application/x-www-form-urlencodedmultipart/form-datatext/plain.
The method was called via a POST request and included a data payload, but the request did not include a Content-Type header.
The team associated with your request is currently undergoing migration to an Enterprise Organization. Web API and other platform operations will be intermittently unavailable until the transition is complete.
The method was called via a POST request, but the POST data was either missing or truncated.
This table lists the expected warnings that this method will return.
However, other warnings can be returned in the case where the service
is experiencing unexpected trouble.
The method was called via a POST request, and recommended practice for the specified Content-Type is to include a charset parameter. However, no charset was present. Specifically, non-form-data content types (e.g. text/plain) are the ones for which charset is recommended.
The method was called via a POST request, and the specified Content-Type is not defined to understand the charset parameter. However, charset was in fact present. Specifically, form-data content types (e.g. multipart/form-data) are the ones for which charset is superfluous.