Send a Facebook Messenger message
POST/v1/communication/messenger/message
Media captions are not supported: companion content.text is discarded for imageUrl, videoUrl, audioUrl and documentUrl. Send the description as a separate text message. Set from to the sandbox keyword or application-channel UUID to send through the application's Messenger Sandbox. to is the external identifier of an active sandbox session. The API key must belong to the application that owns the sandbox channel. Messenger Sandbox accepts text, image, video and audio content. Sandbox errors include SANDBOX_NOT_FOUND, INVALID_SANDBOX_FROM, SANDBOX_APPLICATION_MISMATCH, SANDBOX_SESSION_NOT_FOUND, SANDBOX_SESSION_NOT_CONNECTED, SANDBOX_SESSION_EXPIRED, SANDBOX_CHANNEL_NOT_CONFIGURED, SANDBOX_MESSAGE_LIMIT_REACHED, SANDBOX_CHANNEL_NOT_ALLOWED, SANDBOX_MESSAGE_SEND_FAILED, and UNSUPPORTED_MESSAGE_TYPE. Sandbox media accepts text, mimeType, filename and voice companions. Sandbox responses are enqueued. Public message sends may transfer active/awaiting_human sessions and authorize session billing; typing controls do not persist messages; read controls follow the ordinary persisted outbound path. HTTP validation/authorization/wallet errors use ApiErrorResponse; HTTP 200 status:error is a provider submission failure.
Request
Responses
- 200
- 400
- 401
- 402
- 404
Channel-specific submission result, not a delivery receipt. Typing returns messageId:"". Ordinary read controls persist a new outbound Hub message and return its ID. All Sandbox sends return enqueued.
Invalid payload or CHANNEL_MEDIA_NOT_SUPPORTED for stickerUrl; use imageUrl instead.
Invalid API key
Insufficient wallet balance; message submission or session billing was not authorized.
Application channel not found or does not match the API key