v2.6.16

Teams that run several white-label platforms from one account can now have bot.status_change and bot.chat_message delivered straight to each bot's own callback URL, so each platform only ever receives its own bots' events. The automatic endpoint registration added in v2.6.15 also no longer creates duplicate or stale endpoints.

✨New Features

• Direct per-bot delivery of status and chat events. When enabled on your team, bot.status_change and bot.chat_message are delivered to the callback_config.url of the bot they belong to — exactly one destination per bot — instead of fanning out to the account-level endpoints. This is what you want if one account serves several tenants and each must only see its own traffic. Contact support to have it enabled. See Webhooks.

🐛Bug Fixes

• Automatic registration of callback_config URLs as status endpoints no longer registers the same URL twice, and stale endpoints left behind by an earlier callback URL are reconciled away. Teams using direct per-bot delivery are skipped entirely, so their events are not also fanned out.

↩ All releases