Send a Web Chatt message
POST/v1/communication/web-chatt2me/message
The widget displays content.text below imageUrl, videoUrl or documentUrl, aligned to the left for inbound and outbound messages. Document captions require widget v1.3.3 or later. Audio can be sent, but companion text is not displayed for audioUrl; send its description as a separate text message. Web Chatt supports paymentRequest with PIX, boleto or payment_link. The caller supplies the issued payment details; Hub does not issue or settle payments. Currency defaults to BRL. Payment links accept documented ISO 4217 currencies and offsets; PIX/boleto remain BRL. Amounts use integer minor units; item subtotal and total are validated, and payment links require HTTPS. An orderStatus update resolves the charge by referenceId within the same channel and visitor; optional content.context.messageId selects a specific matching charge. Missing or ambiguous references are rejected. Its bodyText appears as the reply and updates the original charge card. Payment capture and order status remain separate. Sends a message to a visitor through the Web Chatt channel selected by from. Messages for offline visitors are stored as pending and retain the successful sent API response. The API key application must own the selected channel.
Request
Responses
- 200
- 400
- 401
- 402
- 404
Channel-specific submission result, not a delivery receipt. Typing returns messageId:""; Web Chatt read controls return an empty ID without creating a message.
Invalid request payload or insufficient balance.
Missing, invalid, expired, or deleted application API key.
Insufficient wallet balance; message submission or session billing was not authorized.
Application channel not found or not owned by the API key application.