Converse 2.0 MT Messaging API
Send an outbound message to a customer through Converse 2.0. The message is delivered over the channel of the channel account you send it from — WhatsApp, SMS, Email, Viber and others.
Converse 2.0 was formerly known as Moobidesk Enterprise. Hostnames still use the
moobidesk.com domain.
MT is one half of a pair
- MT (this API) — your system sends a message to a customer.
- MO — Converse 2.0 pushes a customer's inbound message to a URL you register.
A working two-way integration needs both. MO is a webhook rather than an endpoint you call, and its payload format is provided by 8x8 when your destination URL is registered.
Authentication
Your apiKey is a path parameter and your apiSecret is a body property:
POST /outgoing/v1/mt/{apiKey}/{channelAccountUUID}
{ "apiSecret": "your-api-secret", ... }
Because the key travels in the URL it can be captured by proxy and server access logs. Restrict who can read logs for systems that call this API, and treat both values as secrets.
Choosing what to send
Exactly one of message, attachments, messageKeyword or type must be present:
| To send | Use |
|---|---|
| Free text | message |
| Files, images, audio or video | attachments |
| A pre-approved canned or template message | messageKeyword (+ parameters) |
| A rich interactive or template message | type + interactive / template |
Response envelope
{ "status": "Ok", "message": "Success" }
{ "status": "Failed", "message": "<error_message>", "data": { "code": 500 } }
A rejected message is still returned with HTTP 200 and status: "Failed" — check the
status property rather than relying on the HTTP status code alone.
Contact
8x8 Converse 2.0: cpaas-sales@8x8.com