The Generic API messaging channel is Dixa's channel for external systems such as chatbots, homegrown messaging platforms, and connectors.
Use this channel when you have your own conversational interface and need to hand conversations off to Dixa agents. Your system drives the interaction via the Dixa API, and Dixa webhooks carry events back to your system. A typical example is a chatbot with its own widget: when a conversation needs human attention, the chatbot imports the conversation into Dixa with the message history, transfers it to an agent queue, and then listens for webhook events to relay agent replies back to the end user.
Messages your system imports with the Import conversation endpoint support three content types:
| Type | Description |
|---|---|
Text | Plain text |
Html | HTML markup |
Markdown | Markdown |
Attachments (images, documents, etc.) are supported as URL references — your system must host the files and pass the URL in the attachments field. Dixa does not store or serve the files.
Agent replies reach your system as Markdown in the data.text field of the Message added webhook, and the webhook's content_type is Markdown. Render the text as Markdown, or convert it to a format your widget supports, before you show it to the end user.
A reply can contain bold, italic, links, bulleted and numbered lists, and line breaks. Underline, text colour and size, headings and tables don't come through: Dixa sends the text without that formatting.
- Audio — the channel is text-only
- Rich message types — buttons, quick replies, and carousels are not supported
- File hosting — Dixa does not accept file uploads; attachments must be publicly accessible URLs hosted by your system