Facts
application/x-www-form-urlencoded application/json Arguments
Required arguments
tokenstringRequiredAuthentication token bearing required scopes. Tokens should be passed as an HTTP Authorization header or alternatively, as a POST parameter.
xxxx-xxxxxxxxx-xxxxchannelstringRequiredChannel containing the message to be updated. For direct messages, ensure that this value is a DM ID (starts with D) instead of a User ID (starts with either U or W).
tsstringRequiredTimestamp of the message to be updated.
"1405894322.002768"Optional arguments
as_userOptionalPass true to update the message as the authed user. Bot users in this context are considered authed users.
trueattachmentsOptionalA JSON-based array of structured attachments, presented as a URL-encoded string.
[{"pretext": "pre-hello", "text": "text-world"}]unfurled_attachmentsOptionalA JSON-based array of structured attachments, presented as a URL-encoded string.
[{"pretext": "pre-hello", "text": "text-world"}]blocksOptionalA JSON-based array of structured blocks, presented as a URL-encoded string.
[{"type": "section", "text": {"type": "plain_text", "text": "Hello world"}}]markdown_textstringOptionalAccepts message text formatted in markdown. This argument should not be used in conjunction with blocks or text. Limit this field to 12,000 characters.
**This is bold text**metadataOptionalJSON object with event_type and event_payload fields, presented as a URL-encoded string. If you don't include this field, the message's previous metadata will be retained. To remove previous metadata, include an empty object for this field. Metadata you post to Slack is accessible to any app or user who is a member of that workspace.
{"event_type": "task_created", "event_payload": { "id": "11223", "title": "Redesign Homepage"}}link_namesOptionalFind and link channel names and usernames. Defaults to none. If you do not specify a value for this field, the original value set for the message will be overwritten with the default, none.
trueparseOptionalChange how messages are treated. Defaults to client, unlike chat.postMessage. Accepts either none or full. If you do not specify a value for this field, the original value set for the message will be overwritten with the default, client.
nonetextOptionalHow this field works and whether it is required depends on other fields you use in your API call. See below for more detail.
Hello worldreply_broadcastbooleanOptionalBroadcast an existing thread reply to make it visible to everyone in the channel or conversation.
falsetruefile_idsarrayOptionalArray of new file ids that will be sent with this message.
F013GKY52QK,F013GL22D0T or ["F013GKY52QK","F013GL22D0T"]Usage info
This method updates a message in a channel. Though related to chat.postMessage, some parameters of chat.update are handled differently.
Ephemeral messages created by chat.postEphemeral or otherwise cannot be updated with this method.
New Slack apps may use this method with the chat:write scope and either a bot or user token.
To define your message, refer to our formatting spec and our guide to composing messages.
text, blocks or attachments
This method will behave differently depending on whether blocks or text is supplied. Slack will always try to render the message using blocks, and use text only for notifications. If you don't include blocks, the message's previous blocks will only be retained if the text argument is not provided. If the text argument is provided and blocks are not provided, the blocks will be removed, and the provided text will be used for message rendering. To remove previous blocks, include an empty array for the blocks field. If blocks are used and a message is being updated, the edited flag will not be displayed on the message (the flag will be displayed on the message if using text).
Similarly, the attachments field is required when not presenting text. If you don't include attachments, the message's previous attachments will be retained. To remove previous attachments, include an empty array for this field.
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.
To use chat.update with a bot users 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.
Response
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.
Updating interactive messages
If you're posting an interactive message, 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, and remove or add blocks.
Typical success response
{
"ok": true,
"channel": "C123ABC456",
"ts": "1401383885.000061",
"text": "Updated text you carefully authored",
"message": {
"text": "Updated text you carefully authored",
"user": "U34567890"
}
}
Typical error response
{
"ok": false,
"error": "cant_update_message"
}
Errors
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 parameter in the response.
access_deniedAccess to a resource specified in the request is denied.
accesslimitedAccess to this method is limited on the current network
account_inactiveAuthentication token is for a deleted user or workspace when using a bot token.
as_user_not_supportedThe as_user parameter does not function with workspace apps.
block_mismatchRich-text blocks cannot be replaced with non-rich-text blocks
blocked_file_typeAdmin has disabled uploading this type of file.
cant_broadcast_messageUnable to broadcast this message.
cant_update_messageAuthenticated user does not have permission to update this message.
channel_not_foundValue passed for channel was invalid.
deprecated_endpointThe endpoint has been deprecated.
edit_window_closedThe message cannot be edited due to the team message edit settings
ekm_access_deniedAdministrators have suspended the ability to post a message.
enterprise_is_restrictedThe method cannot be called from an Enterprise.
external_channel_migratingThe channel is in the process of migrating and so the message cannot be updated at this time.
fatal_errorThe server could not complete your operation(s) without encountering a catastrophic error. It's possible some aspect of the operation succeeded before the error was raised.
file_deletedFile to share deleted.
file_is_deletedThe file is deleted.
file_not_foundOne or more of the provided file IDs could not be found.
file_share_limit_reachedThe file has reached the share limit.
internal_errorThe server could not complete your operation(s) without encountering an error, likely due to a transient issue on our end. It's possible some aspect of the operation succeeded before the error was raised.
invalid_arg_nameThe method was passed an argument whose name falls outside the bounds of accepted or expected values. 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.
invalid_argumentsThe method was called with invalid arguments.
invalid_array_argThe method was passed an array as an argument. Please only input valid strings.
invalid_attachmentsThe attachments were invalid.
invalid_authSome aspect of authentication cannot be validated. Either the provided token is invalid or the request originates from an IP address disallowed from making the request.
invalid_blocksThe blocks were invalid for the requesting user.
invalid_blocks_formatThe blocks array is not a valid JSON object or doesn't match the Block Kit syntax.
invalid_charsetThe method was called via a POST request, but the charset specified in the Content-Type header was invalid. Valid charset names are: utf-8 iso-8859-1.
invalid_form_dataThe method was called via a POST request with Content-Type application/x-www-form-urlencoded or multipart/form-data, but the form data was either missing or syntactically invalid.
invalid_metadata_formatInvalid metadata format provided
invalid_metadata_schemaInvalid metadata schema provided
invalid_post_typeThe method was called via a POST request, but the specified Content-Type was invalid. Valid types are: application/json application/x-www-form-urlencoded multipart/form-data text/plain.
is_inactiveThe message cannot be edited within a frozen, archived or deleted channel.
markdown_text_conflictMarkdown text cannot be used in conjunction with blocks or text argument.
max_file_sharing_exceededExceeded max allowed files shared.
message_limit_exceededMembers on this team are sending too many messages. For more details, see https://slack.com/help/articles/115002422943-Usage-limits-for-free-workspaces.
message_not_foundNo message exists with the requested timestamp.
metadata_must_be_sent_from_appMessage metadata can only be posted or updated using an app-level token
metadata_too_largeMetadata exceeds size limit
method_deprecatedThe method has been deprecated.
missing_post_typeThe method was called via a POST request and included a data payload, but the request did not include a Content-Type header.
missing_scopeThe token used is not granted the specific scope permissions required to complete this request.
msg_too_longMessage text is too long. The text field cannot exceed 4,000 characters.
no_dual_broadcast_content_updateCan't broadcast an old reply and update the content at the same time.
no_permissionThe workspace token used in this request does not have the permissions necessary to complete the request. Make sure your app is a member of the conversation it's attempting to post a message to.
no_textNo message text provided
not_allowed_token_typeThe token type used in this request is not allowed.
not_authedNo authentication token provided.
org_login_requiredThe workspace is undergoing an enterprise migration and will not be available until migration is complete.
posting_to_channel_deniedThe user does not have permission to share files in this channel.
ratelimitedThe request has been ratelimited. Refer to the Retry-After header for when to retry the request.
request_timeoutThe method was called via a POST request, but the POST data was either missing or truncated.
service_unavailableThe service is temporarily unavailable
slack_connect_blocked_file_typeFiles with certain extensions are blocked from being uploaded in all Slack Connect messages.
slack_connect_canvas_sharing_blockedAdmin has disabled sharing of canvas links in all Slack Connect messages.
slack_connect_clip_sharing_blockedAdmin has disabled Clip uploads in Slack Connect channels.
slack_connect_file_link_sharing_blockedAdmin has disabled Slack file sharing in all Slack Connect messages.
slack_connect_file_upload_sharing_blockedAdmin has disabled file uploads in all Slack Connect messages.
streaming_state_conflictThe message is currently streaming text and cannot be edited.
team_access_not_grantedThe token used is not granted the specific workspace access required to complete this request.
team_added_to_orgThe workspace 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.
team_not_foundTeam associated with the message and channel could not be found.
token_expiredAuthentication token has expired
token_revokedAuthentication token is for a deleted user or workspace or the app has been removed when using a user token.
too_many_attachmentsToo many attachments were provided with this message. A maximum of 100 attachments are allowed on a message.
two_factor_setup_requiredTwo factor setup is required.
unable_to_share_filesSharing the files failed.
update_failedInternal update failure.