Skip to main content
POST
/
api
/
v1
/
bots
/
{object_id}
/
send_chat_message
Send Chat Message
curl --request POST \
  --url https://api.example.com/api/v1/bots/{object_id}/send_chat_message \
  --header 'Content-Type: application/json' \
  --data '
{
  "message": "<string>",
  "to": "<string>",
  "to_user_uuid": "<string>"
}
'
Causes the bot to send a chat message in the meeting.

Authentication

Requires API key authentication via the Authorization header.

Path Parameters

object_id
string
required
Bot ID (e.g., bot_xxxxxxxxxxx)

Request Body

message
string
required
The message text to send. Currently does not support emojis. For Microsoft Teams, you can use basic HTML tags including <p>, <br>, <b>, <i>, and <a>.
to
string
default:"everyone"
Who to send the message to. Options:
  • everyone - Send to all participants
  • specific_user - Send to a specific user (requires to_user_uuid)
  • everyone_but_host - Send to all participants except the host
to_user_uuid
string
The UUID of the user to send the message to. Required when to is set to specific_user.

Response

Returns a 200 status code when the chat message request is successfully created.

Example Request - Everyone

curl -X POST https://app.attendee.dev/api/v1/bots/bot_weIAju4OXNZkDTpZ/send_chat_message \
  -H "Authorization: Token YOUR_API_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "everyone",
    "message": "Hello everyone, I am here to record and summarize this meeting."
  }'

Example Request - Specific User

curl -X POST https://app.attendee.dev/api/v1/bots/bot_weIAju4OXNZkDTpZ/send_chat_message \
  -H "Authorization: Token YOUR_API_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "specific_user",
    "to_user_uuid": "123e4567-e89b-12d3-a456-426614174000",
    "message": "Hello Bob, I am here to record and summarize this meeting."
  }'

Example Request - Teams with HTML

curl -X POST https://app.attendee.dev/api/v1/bots/bot_weIAju4OXNZkDTpZ/send_chat_message \
  -H "Authorization: Token YOUR_API_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "everyone",
    "message": "<p><b>Meeting Bot</b></p><p>Recording in progress. Visit <a href=\"https://example.com\">dashboard</a> for details.</p>"
  }'

Error Responses

400 Bad Request

Returned when:
  • Missing required fields
  • Invalid to value
  • to_user_uuid missing when to is specific_user

404 Not Found

Returned when the bot ID does not exist.
The bot must be actively in a meeting to send chat messages. Messages are sent through the meeting platform’s native chat interface.

Build docs developers (and LLMs) love