Sending Messages
In this section, you will find a brief comparison between Cloud API and MM Lite, along with step-by-step instructions on how to send Marketing Messages using the MM Lite Beta API.
Last updated
Was this helpful?
In this section, you will find a brief comparison between Cloud API and MM Lite, along with step-by-step instructions on how to send Marketing Messages using the MM Lite Beta API.
Last updated
Was this helpful?
The /marketing_messages endpoint supports only Marketing template messages. All other message types (freeform, Authentication, Service, Utility) are not supported, and will produce an error.
To send Marketing templates, only the URL must be changed when compared with Cloud API. The body content of the message should remain:
https://waba-v2.360dialog.io/messages
https://waba-v2.360dialog.io/marketing_messages
For details on the template body, you can check the, as the MM Lite API uses the same API payload syntax and requires the same permissions:
To send a template message you will need to use a POST request:
POSThttps://waba-v2.360dialog.io/marketing_messages
Content-Type
application/json
D360-API-KEY
Bearer <token>
D360-API-KEY received after approval to participate in this program
messaging_product
Yes
"whatsapp"
recipient_type
Yes
"individual"
to
Yes
Recipient phone number in international format. Example: "441234567890"
type
Yes
"template"
template.name
Yes
"marketing_text_no_param"
template.language.code
Yes
"en"
template.language.policy
Yes
"deterministic"
message_activity_sharing
Optional
Set to true to enable activity sharing (can be removed if not needed)
Response
An usual Cloud API response is expected after a successful message sent using MM Lite API.
MM Lite API provides additional features that are not available to Marketing templates on Cloud API.
This means you can include and set the value of the message_send_ttl_seconds in the payload of your Marketing Message Template to test this feature.
After a Marketing Template is created for the phone number, it may take up to 10 minutes to sync with the connected Ad account. This sync enables message optimization and conversion tracking. The same delay applies if a template has been inactive for more than 7 days—sync will resume after the first new use.
To ensure proper delivery and tracking, wait a bit more than 10 minutes before sending marketing traffic with a newly created or reactivated template. MM Lite API supports all active Marketing templates.
For MM Lite API it is possible to add a new property at the message level that toggles on/ off sharing message activities (e.g. message read) for that specific Marketing Message to Meta to help optimize marketing messages.
If this parameter is not provided, the default WABA-Level setting will be applied.
“message_activity_sharing”: <true / false>
You can always edit your default setting in Business Settings on Facebook Manager.
Messages sent through MM Lite may take longer to be delivered. This is because MM Lite uses an automated and optimized delivery system developed by Meta.
As part of this optimization process, additional processing steps are introduced, which may result in slight delays. The system is designed to prioritize message delivery to users who are more likely to engage, rather than delivering to all recipients immediately.
Please note:
Not all clients are guaranteed to receive every message.
Delivery is based on Meta’s optimization algorithm, which selects the most relevant recipients.
You can continue to use the same method you already use to create the .
Learn more about this limitation here:
You can learn more about how this delivery model works in the.