Send a Message
Send a message to an existing chat. (Only if the dialogue has an Open Session). The message will be added to the queue for sending and delivered even if the phone is disconnected from the Internet or authorization is not passed.
Only one destination parameter is needed - chatId, phone, or bsuid. In BSUID-centric routing, chatId can be [email protected], bsuid@lid, [email protected], or username@username. The phone field accepts a phone number or BSUID; bsuid can be passed separately.
Direct Send is in beta. Meta has not enabled it on every business portfolio, so category and directSend are a beta option: watch delivery errors before relying on them.
Set category to utility or authentication to send outside the 24-hour window as a Meta Direct Send template instead of the 1MSG marketing auto-template. authentication is part of that beta and is not recommended. directSend.serviceFirst: true tries a free service message first and uses Direct Send only when Meta rejects it because the window is closed (131047). directSend.templateName is only valid with utility (^[a-z0-9_]+$, max 512). Direct Send text is limited to 1024 characters. Without templateName, the first unseen phrase may be delivered as Meta's onboarding template. A named template does not guarantee delivery — wait for webhook errors 131000 or 132021. An open 24-hour window is still billed as utility when category is set and serviceFirst is not true.
JWT tokentoken<token>- body
body*stringMessage text, UTF-8 or UTF-16 string with emoji 🍏. Can be used with mentionedPhones, example: this text for @556123122026
category?stringOptional Direct Send category. Direct Send is in beta: Meta has not enabled it on every business portfolio. utility or authentication enables it. authentication is part of that beta and is not recommended. Omit or service keeps a normal service message. marketing is rejected.
"utility""authentication""service"directSend?Optional. Ignored unless category is utility or authentication. serviceFirst is not forwarded to Meta.
quotedMsgId?stringQuoted message ID (Cloud API)
chatId?stringRequired if phone and bsuid are not set
Chat ID from the message list. Examples: [email protected], RU.1504711984690866@lid, username@username, or [email protected] (group). Used instead of the phone parameter.
phone?stringRequired if chatId and bsuid are not set
Recipient identifier. Accepts a phone number starting with the country code, or a BSUID such as RU.1504711984690866.
Use chatId for full chat IDs: [email protected], bsuid@lid, username@username, or [email protected].
bsuid?stringOptional alternative to phone/chatId
Recipient BSUID without the @lid suffix. Example: RU.1504711984690866.
Server response example
application/json- response
sent?booleanid?stringunique message id
message?stringPosting status message
description?stringResult description
curl -X POST 'https://api.1msg.io/123/sendMessage' \ -H 'Content-Type: application/json' \ -d '{ "body": "Hello World", "phone": "12020721369"}'{ "sent": true, "id": "gBGGeRhGZTEfAgkJCh2wAz4ZH-8", "message": "Sent to [email protected]", "description": "Message has been sent to the provider"}