Chat: Expose a public REST API and webhooks for replies, assignment and resolve
Intercom's REST API covers conversations (list, search, reply, assign, close, snooze, tag, notes), contacts and tags (https://developers.intercom.com/docs/references/rest-api/api.intercom.io/conversations), and Chatwoot exposes an equivalent open API. Our public API in app/api/v1 has agents, calendar, crm and links but no chat, and emitEvent is only called in lib/chat-visitor-message.ts for conversation.created and message.received; agent replies, assignment changes and resolve emit nothing. Developers self-hosting the suite (persona 2 in PRODUCT.md) expect to pipe chats into Slack, Flow or their own tools. First scope: GET/POST /api/v1/chat/conversations and messages with API keys, plus message.sent, conversation.assigned and conversation.resolved events, documented in openapi.json. Priority: medium. Effort: M. Compared with Intercom.
Comments 0
No comments yet.
Sign in to comment