List of messages for a conversation sorted from oldest to newest
- Add message
Dixa API (v1)
Request
Get all messages for a particular conversation by providing the conversation id. Note that messages in ContactForm conversations can have attributes of "_type": "EmailAttributes" if they are created through a webform, or "_type": "ContactFormAttributes" when created through a chat widget.
- Mock serverhttps://docs.dixa.io/_mock/openapi/dixa-api/v1/v1/conversations/{conversationId}/messages
- https://dev.dixa.io/v1/conversations/{conversationId}/messages
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://docs.dixa.io/_mock/openapi/dixa-api/v1/v1/conversations/{conversationId}/messages' \
-H 'Authorization: YOUR_API_KEY_HERE'- Email messages example (Regular and TooLarge content)
- Chat message example
- Contact form message example
- Messenger form message example
- Phone message example
- Call recording message example
- SMS message example
- Facebook Messenger message example
- WhatsApp message example
- Generic message example
{ "data": [ { … }, { … } ] }
Request
Add a message to a conversation. For inbound messages the author is assumed to be the requester of the conversation (end user). For outbound messages the author is specified using the agentId field.
If attachments are added to the message, they will be copied and stored in Dixa.
Supported channels are Chat, Messenger, Contact Form, Email, Sms (outbound only), Whatsapp (outbound and Markdown only).
Supported Markdown syntax for Markdown content: bold **text**, italic *text*, bold & italic ***text***, strikethrough ~text~, blockquote > Quoted text. \n Message about quoted text, ordered list List:\n1. Item\n2. Item\n3. Item, unordered list List:\n* Item\n* Item\n* Item, inline code This is `code`.
Whatsapp channel:
Only one attachment is allowed per WhatsApp message.
Supports the following file types for attachments: .jpg, .jpeg, .png, .pdf, .doc, .docx, .pptx, .xlsx
The message to be added to a conversation
Only Outbound messages are supported for Sms and Whatsapp.
Internal email address registered for the integration with format: <email-address>@email.dixa.io
- Mock serverhttps://docs.dixa.io/_mock/openapi/dixa-api/v1/v1/conversations/{conversationId}/messages
- https://dev.dixa.io/v1/conversations/{conversationId}/messages
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
- General inbound example
- General outbound example
- Whatsapp outbound
- Whatsapp outbound with attachments
curl -i -X POST \
'https://docs.dixa.io/_mock/openapi/dixa-api/v1/v1/conversations/{conversationId}/messages' \
-H 'Authorization: YOUR_API_KEY_HERE' \
-H 'Content-Type: application/json' \
-d '{
"content": {
"value": "I need some help!",
"_type": "Html"
},
"attachments": [
{
"url": "http://attachment.url",
"prettyName": "Filename"
}
],
"_type": "Inbound"
}'{ "data": { "content": { … }, "direction": "Outbound", "authorId": "bac5a02c-15b3-44da-ae1e-ab7b9db4aa89", "messageId": "87bac308-e49f-4134-84cc-96b868f1e1e4", "createdAt": "2021-06-09T08:18:37.284Z" } }
Request
Create a conversation. For inbound messages the author is assumed to be the requester of the conversation (end user). For outbound messages the author is specified using the agentId field.
The conversation to create
- Mock serverhttps://docs.dixa.io/_mock/openapi/dixa-api/v1/v1/conversations
- https://dev.dixa.io/v1/conversations
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
https://docs.dixa.io/_mock/openapi/dixa-api/v1/v1/conversations \
-H 'Authorization: YOUR_API_KEY_HERE' \
-H 'Content-Type: application/json' \
-d '{
"requesterId": "9c2a2cce-699f-4a72-89d9-fda5bc8dec8b",
"emailIntegrationId": "my-integration@email.dixa.io",
"subject": "order #123",
"message": {
"content": {
"value": "My order hasn'\''t shipped",
"_type": "Text"
},
"attachments": [],
"_type": "Inbound"
},
"language": "en",
"_type": "Email"
}'{ "data": { "id": 100 } }