Onboarding and Sending Messages
This documentation aims to guide you on how to onboard in Meta’s Marketing Messages API.
Marketing Messages API for WhatsApp (formerly known as Marketing Messages Lite API) is now generally available.
In MM API, we call onboarding the process where the client reviews and accepts the MM API Terms of Service. The Onboarding is always performed at a Business Manager level. Please see the next steps to onboard to MM Lite:
Onboarding Link in the Client Hub
To streamline client onboarding, you will now see a banner in the Client Hub. This banner contains a unique button that you can easily click to begin the MM API onboarding process.
How to do that?
To access the onboarding link, log in to your client account here
Important: This step requires the client to be an administrator of the Business Portfolio or Business Manager.
The terms accepted in this process will apply to all existing WhatsApp Business Accounts (WABAs) under the selected Business Manager. Clients with multiple Business Managers must repeat the process for each BM.
Self-Onboard using WhatsApp Manager
What is it?
This is the best way to get access to the MM API feature. In this case, you can use the WhatsApp Business Manager to accept the terms.
How it works
Sending Messages with MM API
To send a template message, you will need to use a POST request:
POSThttps://waba-v2.360dialog.io/marketing_messages
The only difference is the endpoint /marketing_messages, and it should be used only for Marketing messages.
Headers
Content-Type
application/json
D360-API-KEY
Bearer <token>
D360-API-KEY received after approval to participate in this program
Body
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)
Request example
Response
The same response from the Cloud API is expected after a successful message is sent using the MM API.
Sending a Marketing Template Message with TTL using MM API
MM 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.
Handling Webhooks
With MM API, you don’t need to change your webhook setup. You will keep receiving the usual events (sent → delivered → read) the same way as with the Cloud API.
The only difference: when you send via /marketing_messages with "message_activity_sharing": true, you also get a click event whenever a user taps the CTA link in your template.
This makes it easier to track performance and optimize campaigns without changing your current logic.
At the moment, it’s not possible to know which phone number clicked. You only get the event itself.
Webhook events received:
This event includes the value "marketing_lite" to indicate that it was sent using the MM Lite API:
Last updated
Was this helpful?


