Messaging

Send messages to individuals, teams, or channels through Dailybot. Thesend-message endpoint powers text messages, images, buttons, thread replies, bot impersonation, and edit-in-place — all through a single POST. Messages are delivered on the platform your organization connected (Slack, Microsoft Teams, Discord, or Google Chat).

Send Message

curl -X POST "https://api.dailybot.com/v1/send-message/" \
  -H "X-API-KEY: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "Deployment completed successfully! ✅",
    "target_users": ["a1b2c3d4-e5f6-7890-abcd-ef1234567890"],
    "target_teams": ["b2c3d4e5-f6a7-8901-bcde-f12345678901"]
  }'

{
  "bot_message_id": "$db/ae007b43-dde2-4fa9-bce3-71fb0975a249"
}

{
  "detail": "cli_send_message_target_not_allowed",
  "code": "cli_send_message_target_not_allowed"
}

Threaded replies

Two ways to thread. Pass `thread_responses` (up to 10) to publish a parent plus replies in a single call. Each reply ID comes back in the response for later editing.

To reply inside an existing thread, use the object form of `target_channels` and set `thread` to the parent timestamp/id.

curl -X POST "https://api.dailybot.com/v1/send-message/" \
  -H "X-API-KEY: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "Release 4.12.0 shipping now.",
    "target_channels": ["C0123456789"],
    "thread_responses": [
      {"message": "Frontend: build passed"},
      {"message": "Backend: migrations OK"},
      {"message": "Full changelog: https://acme.example/rel/4.12.0"}
    ]
  }'

curl -X POST "https://api.dailybot.com/v1/send-message/" \
  -H "X-API-KEY: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "One caveat: enable feature flag \"nav_v2\" first.",
    "target_channels": [
      { "id": "C0123456789", "thread": "1710000000.123456" }
    ]
  }'

{
  "bot_message_id": "$db/ae007b43-dde2-4fa9-bce3-71fb0975a249",
  "thread_responses": [
    "$db/thread-1",
    "$db/thread-2",
    "$db/thread-3"
  ]
}

Bot impersonation (Slack)

`platform_settings.bot_username` together with `bot_icon_url` OR `bot_icon_emoji` changes the bot display for the message. Slack only today — other platforms silently ignore the block and use the connected bot identity.

curl -X POST "https://api.dailybot.com/v1/send-message/" \
  -H "X-API-KEY: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "Deployed 4.12.0 to production ✅",
    "target_channels": ["C0123456789"],
    "platform_settings": {
      "bot_username": "Release Bot",
      "bot_icon_emoji": ":rocket:"
    }
  }'

Editing a message

Re-POST the endpoint with the same `bot_message_id` within **72 hours** to edit the original. Works on the parent as well as on any of its `thread_responses` IDs.

curl -X POST "https://api.dailybot.com/v1/send-message/" \
  -H "X-API-KEY: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "bot_message_id": "release-4.12.0",
    "message": "Deployed 4.12.0 — rollback in progress ⚠️",
    "target_channels": ["C0123456789"]
  }'

Ephemeral messages (Slack)

Set `platform_settings.is_ephemeral: true` together with `target_users` to post a message inside the specified channel that only those users see. Slack-only feature; other platforms treat it as a normal message.

curl -X POST "https://api.dailybot.com/v1/send-message/" \
  -H "X-API-KEY: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "Heads-up: your on-call rotation starts in 10 minutes.",
    "target_channels": ["C0123456789"],
    "target_users": ["a1b2c3d4-e5f6-7890-abcd-ef1234567890"],
    "platform_settings": { "is_ephemeral": true }
  }'

send_as_user identity override (Slack only)

send_as_user lets an authorized caller post a message that appears to come from another user — the message shows that user's Slack display name and profile picture instead of the Dailybot bot identity.

The message is still delivered through the Dailybot bot token (it does not use the target user's own Slack token), so it respects the bot's channel access and Slack's bot-message attribution rules.

• Caller must be an organization admin (or have a key owned by an admin).
• The target user (send_as_user UUID) must be active and in the same organization.
• Slack only — other platforms silently fall back to the standard bot identity.
• send_as_user is mutually exclusive with bot_username, bot_icon_url, and bot_icon_emoji.

curl -X POST "https://api.dailybot.com/v1/send-message/" \
  -H "X-API-KEY: $DAILYBOT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "The sprint is closed and all tickets are resolved.",
    "target_channels": ["C0123456789"],
    "send_as_user": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
  }'

Use cases

• Automated standup summaries posted under the team member's name.
• AI-generated check-in reminders attributed to the manager.
• Workflow outputs attributed to the user who triggered them.

CLI role scoping

When the caller is a CLI-authenticated user (not a machine API key), Dailybot enforces role-based reach: admins and managers can target any user/team/public channel; team members can target their shared-team members plus public channels; guests can only send to themselves. Sending outside that scope returns 403 with error `cli_send_message_target_not_allowed`.

Send Email

curl -X POST "https://api.dailybot.com/v1/send-email/" \
  -H "X-API-KEY: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "users_uuids": ["a1b2c3d4-e5f6-7890-abcd-ef1234567890"],
    "email_subject": "Weekly Report Ready",
    "email_content": "Your weekly team report is now available. Check your dashboard."
  }'

{
  "detail": "Emails sent successfully."
}

{
  "detail": "one_or_more_users_not_found",
  "code": "one_or_more_users_not_found"
}

{
  "detail": "Invalid or missing API key.",
  "code": "authentication_failed"
}

Open Conversation

curl -X POST "https://api.dailybot.com/v1/open-conversation/" \
  -H "X-API-KEY: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "users_uuids": [
      "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
      "b2c3d4e5-f6a7-8901-bcde-f12345678901"
    ]
  }'

{
  "channel": "C0123456789"
}

{
  "detail": "one_or_more_users_not_found",
  "code": "one_or_more_users_not_found"
}

{
  "detail": "Invalid or missing API key.",
  "code": "authentication_failed"
}