Updates a message.


Method URL:
Preferred HTTP method:POST
Accepted content types:application/x-www-form-urlencoded, application/json
Rate limiting:Tier 3
Works with:
Token typeRequired scope(s)
userchat:write  chat:write:bot  chat:write:user 
classic botbot

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.



Authentication token bearing required scopes.


Channel containing the message to be updated.


Timestamp of the message to be updated.


Pass true to update the message as the authed user. Bot users in this context are considered authed users.


A JSON-based array of structured attachments, presented as a URL-encoded string. This field is required when not presenting text.

Example[{"pretext": "pre-hello", "text": "text-world"}]

A JSON-based array of structured blocks, presented as a URL-encoded string.

Example[{"type": "section", "text": {"type": "plain_text", "text": "Hello world"}}]

Find and link channel names and usernames. Defaults to none. See below.


Change how messages are treated. Defaults to client, unlike chat.postMessage. Accepts either none or full. See below.


New text for the message, using the default formatting rules. It's not required when presenting attachments.

ExampleHello world

This method supports application/json via HTTP POST. Present your token in your request's Authorization header. Learn more.


By default, Slack will attempt to discover links in text but does not support URL markup. To update messages with URL markup, you must specify link_names=1 or parse=none. Names and channels will not be linkified in the @username or #channel format, unless you pass link_names=1 or parse=full. For more information, refer to the formatting spec.

If you used link_names or parse arguments in the original message, you should specify them when calling chat.update as well. Otherwise, the values you passed initially will be overwritten with this method’s defaults (link_names=none, parse=client).

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.


Typical success response

    "ok": true,
    "channel": "C024BE91L",
    "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"

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.

Bot users

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.


Internal update failure.


Value passed for channel was invalid.


Team associated with the message and channel could not be found.


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


The as_user parameter does not function with workspace apps.


The message cannot be edited within a frozen, archived or deleted channel.


The blocks were invalid for the requesting user.


The attachments were invalid.


The channel is in the process of migrating and so the message cannot be updated at this time.


No authentication token provided.


Some 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.


Authentication token is for a deleted user or workspace.


Authentication token is for a deleted user or workspace or the app has been removed.


The 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.


The workspace is undergoing an enterprise migration and will not be available until migration is complete.


Administrators have suspended the ability to post a message.


The token used is not granted the specific scope permissions required to complete this request.


The method was called with invalid arguments.


The 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.


The 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.


The 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.


The 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.


The method was called via a POST request and included a data payload, but the request did not include a Content-Type header.


The 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.


The method was called via a POST request, but the POST data was either missing or truncated.


The 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.


The 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.


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 text field of a message should have no more than 40,000 characters. We truncate really long messages.


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.