Post to a chat
POST/chat.post
Post a message to a chat. Messages can be plain markdown text, rich Block Kit layouts, or polls.
Messages may be posted to a chat, a group, or one or more addresses (e.g. users, bots).
Mentions are supported with the syntax <@USER_ID>, e.g. <!@U-7861a4c6-765a-495d-898d-fae3d8fbba2d> or <@all> to notify everyone in the chat.
When rendered in the client, the tag will automatically be replaced with the human-readable display name (or "everyone" for <@all>).
Access: Organization and Personal. In Organization mode, messages are sent with the app's bot persona. In Personal mode, messages are sent as the authenticated user.
Required scope: chat:send_message or chat:write
OpenAPI Spec: chat.json
Request
Responses
- 200
- 400
- 401
- 403
- 405
- 413
- 500
Info retrieved successfully sent
Bad request. Common causes:
- Invalid chat/group/address ID
threadTimestampdoes not correspond to an existing message- Both
threadKeyandthreadTimestampwere provided (they are mutually exclusive) threadKeyexceeds 64 charactersreplyTimestampused on a top-level channel message (only allowed in DMs or within a channel thread)replyTimestampcombined withblocksorpoll(text messages only)- Invalid bot code format
- Multiple content types provided (only one of
text/items,blocks, orpollallowed) blocksarray exceeds 10 blocks or 8,000 bytes- Invalid block structure (see Block Kit guide)
- Interactive buttons sent without an Interactivity URL configured
- Invalid
colorvalue - Poll question empty or exceeds 256 characters
- Poll has fewer than 2 options, or an option exceeds 128 characters
Presented invalid authentication credentials.
Forbidden. The bot lacks access to the target:
- Bot is not a member of the chat or group
- Group does not exist in your Roam
An unsupported method was requested.
Message content exceeds the maximum allowed size.
An internal error occured.