MM Lite versus Cloud API
Let’s see how sending a marketing message works with the Cloud API — and how easy it is to do the same with MM Lite
📑Main Difference: Just the Endpoint!
“You only need to update your endpoint to start using MM Lite.”
Product comparison
Delivery Optimization
Not supported
✅ Equal or better delivery rates
TTL for Marketing Messages
Not supported
✅ Supported (exclusive to MM Lite)
Risk of Delivery Restrictions
Same as current usage
✅ Lower risk of flagging
Best Use Cases
Basic or operational campaigns
✅ High-volume, performance-driven campaigns
Technical comparison
Base URL
https://waba-v2.360dialog.io
Identical
Endpoint to be used
/messages
/marketing_messages
Authentication
Same API Key
Same API Key
Payload Format
Identical
Identical
Webhook Behavior
Same structure
Same structure1
Additional details related to the cost of MM Lite are included as an informative property.
🧪Try It Yourself
We recommend running your own tests by switching your endpoint and observing the results.
✅ No need to change payloads
✅ No need to change webhook logic
✅ Keep your existing token
MM Lite is designed to make your life easier. Start small: test one flow, and evaluate performance gains.
Sending a marketing message using the Cloud API
curl --location 'https://waba-v2.360dialog.io/messages' \
--header 'D360-API-KEY: <api_key>' \
--header 'Content-Type: application/json' \
--data '{
"to": "<end_client_number>",
"type": "template",
"template": {
"name": "<template_name>",
"language": {
"code": "<template_language_code>"
},
"components": []
},
"messaging_product": "whatsapp"
}'
☝️As you may know, we typically expect to receive three webhooks: sent, delivered, and read. However, when a user clicks the link inside a marketing template message sent via the Cloud API, no webhooks are triggered at all.
⚡Now let´s see how it works when we send the same marketing template message using the MM Lite API:
Sending a marketing message using the MM Lite API
curl --location 'https://waba-v2.360dialog.io/marketing_messages' \
--header 'D360-API-KEY: <API_KEY>' \
--header 'Content-Type: application/json' \
--data '{
"messaging_product": "whatsapp",
"recipient_type": "individual",
"to": "<end_client_number>",
"type": "template",
"template": {
"name": "<template_name>",
"language": {
"policy": "deterministic",
"code": "<template_language_code>"
}
},
"message_activity_sharing":true
}'
⚠️If you see, we only need to use a different endpoint; nothing else is required. The same webhooks are returned, but with a big change: we collect the click event.
Last updated
Was this helpful?