MM Lite Alpha Sandbox Testing

Pre-Requisites

To avoid all pre-requisites required to participate in MM Lite Alpha, 360Dialog will provide a testing number already registered in one of the supported geographies.

Goal

The goal of MM Lite Alpha Sandbox Testing is to help Partners prepare their platforms for the required changes to access MM Lite new features before release.

It is expected, that the Partner can compare sending marketing messages using Cloud API (current way of sending Marketing Messages) vs MM Lite, and get all the expected error codes to have a full support managing all the different message variations.

1

How to Access

• Write an email to [e-mail] requesting for access to the MM Lite test environment.

• Wait for the alpha-beta Team to reply to you in maximum 3 days.

2

What You Will Receive

• A phone number pre-registered with MM Lite Alpha access enabled.

• Templates pre-created.

• 360dialog API Authentication Key (D360-API-Key).

3

Limitations

What you can do in the Sandbox

• You can use the test phone number to send messages and templates to your own phone number.

• A limited amount of messages can be sent with the sandbox test phone number.

• Your phone number acts like a user and can send and receive messages.

• You can switch the webhook notifications endpoint at any time. If you don't have one yet you can use a free service like RequestBin to set up an endpoint.

What you can't do with the Sandbox

• The Sandbox is a test environment only. Each Sandbox API Key is rate limited, not supporting bulk messaging. Bad usage detected can generate extra charges.

• You do not have access to the FBM or the Hub of this WABA, only the API.

• The Sandbox number is hosted in the Cloud API. If you require assistance, please reach out to our Team at [e-mail].

Getting Started

Minimum Conditions

A Business’ BMID must satisfy the condition:

1. Have the destination phone number based in one of the following geographies: Brazil, Mexico, India, Indonesia, Peru, Chile.

How It Works

1. Pre-requisites validation: sending and receiving messages using Cloud API

a. [optional - recommended] → Setup a webhook listener to receive all notifications associated with messages sent by the business.

b. Receiving a simple text message from a user

c. Reply to the user with a simple text message

d. Sending a Marketing Template Message using Cloud API

2. Sending the first MM Lite Marketing Message

a. Sending a Marketing Template Message using MM Lite API

b. Sending a Marketing Template Message with TTL using MM Lite API

c. Creating new Marketing Templates

3. Expected Errors

a. Using MM Lite API to send normal text messages

b. Using MM Lite API to send Authentication or Utility templates

c. Not allowed to send messages using MM Lite API

d. Using the wrong D360-API-KEY

4. Examples using multiple programming languages

a. NodeJS

b. Python

c. Postman Testing collection

See below each step described:

---

1. Sending and receiving messages using Cloud API

a. [optional - recommended] → Setup a webhook listener to receive all notifications associated with messages sent by the business

When you send a message, your webhook will receive status updates such as sent, delivered, and read. If you send a message to the Sandbox number from your personal WhatsApp account, your webhook will also receive the incoming message event.

i. How to visualize webhook notifications

You can use an external service (such as Webhook.site - Test, transform and automate Web requests and emails ) to test webhook responses, or you can create your own webhook server for tests.

In the case you want to test with localhost, you may use an external service (such as ngrok).

Example:

Open Webhook.site - Test, transform and automate Web requests and emails in your browser.

a unique URL will be generated automatically. In this example it was: https://webhook.site/d4d4df6d-ee02-4572-a021-bcc60836d1e7

ii. Test Webhook URL

To validate that you are ready to receive incoming webhook notifications on that unique URL, you can do a simple cURL using a terminal as it appears on their Examples page.

The URL that appears in this example must be updated with the unique URL generated in the previous step.

curl -X POST 'https://webhook.site/' \
  -H 'content-type: application/json' \
  -d $'{"id": 7, "company": "360Dialog", "initiative": "Alpha Sandbox Testing MM Lite API"}'

The webhook notification should appear as in this example:

iii. Set Webhook URL To start redirecting any webhook notification generated by the Sandbox test number, it is required to execute a POST request passing the expected URL as the ‘URL’ parameter.

POSThttps://waba-v2.360dialog.io/waba_webhook

Headers

Name	Value	Description
Content-Type	application/json
D360-API-KEY	Bearer <token>	D360-API-KEY received after approval to participate in this program

Body

Name	Type	Description
url	string	Your unique URL generated in the previous step.

curl --location 'https://waba-v2.360dialog.io/waba_webhook' \
--header 'Content-Type: application/json' \
--header 'D360-API-KEY: <token>' \
--data '{
    "url": "https://webhook.site/d4d4df6d-ee02-4572-a021-bcc60836d1e7" //unique URL
}'

Response

200

{
    "message": "Webhook will be set for waba_id: xxxxxxxxxxxxx"
}

iv. Check Webhook URL

To check the current URL associated with webhooks, execute the GET request:

GEThttps://waba-v2.360dialog.io/waba_webhook

Headers

Name	Value	Description
Content-Type	application/json
D360-API-KEY	Bearer <token>	D360-API-KEY received after approval to participate in this program

curl --location 'https://waba-v2.360dialog.io/waba_webhook' \
--header 'Content-Type: application/json' \
--header 'D360-API-KEY: <token>'

Response

200

{
    "url": "https://webhook.site/d4d4df6d-ee02-4572-a021-bcc60836d1e7", //your url
    "headers": null,
    "waba_id": "9966xxxxxx28593064",
    "phone_numbers": [
        "<< SANDBOX TEST PHONE NUMBER >> "
    ]
}

b. Receiving a simple text message from a user

To initiate the conversation, it's easier to send a message from your personal WhatsApp account to the Sandbox number. You should see this message appear in your webhook listener as a new incoming event.

1. Open your personal WhatsApp app and create a new contact using the Sandbox phone number provided by our Team.

2. Send a simple message, such as “Hello,” to the Sandbox number.

3. The message should appear as an incoming webhook event in your webhook listener.

c. Reply to the user with a simple text message

As an example of replying back to the user, we will send a simple text message from our Sandbox number, expecting it will appears as a conversation in the personal WhatsApp App.

To send a text message using Cloud API, a POST request is required.

POSThttps://waba-v2.360dialog.io/messages

Headers

Name	Value	Description
Content-Type	application/json
D360-API-KEY	Bearer <token>	D360-API-KEY received after approval to participate in this program

Body

Name	Value
messaging_product	whatsapp
recipient_type	individual
to	User phone number. International Prefix code is expected, like: 441234567890
type	text
text
body	Write a simple text message for testing

curl --location 'https://waba-v2.360dialog.io/messages' \
--header 'Content-Type: application/json' \
--header 'D360-API-KEY: <token>' \ //your
--data '{
    "messaging_product": "whatsapp",
    "recipient_type": "individual",
    "to": "<<RECIPIENT_PHONE_NUMBER>>", //phone number with prefix
    "type": "text",
    "text": {
        "body": "This is a simple text msg send using cloud api"
    }
}'

Response

An usual response is expected after a successful message sent using Cloud API

200

{
    "messaging_product": "whatsapp",
    "contacts": [
        {
            "input": "<phone number>",
            "wa_id": "<<waba id>"
        }
    ],
    "messages": [
        {
            "id": "wamid.HBgLNTk4OTQ3MTQ0NjMVAgARGBJDNjM1NUM2OEEyMDU4REZERTgA"
        }
    ]
}

You should expect the following Webhook notifications to be received after a successful message received and read by the user:

• Message Sent Webhook Notification

• Message Delivered Webhook Notification

• Message Read Webhook Notification

d. Sending a Marketing Template Message using Cloud API

Each Sandbox phone number has a suite of pre-defined templates.

In this step, we will send a simple template with the following characteristics:

Body

Name	Value
category	whatsapp
template name	marketing_text_no_param
template language	en
header	none
body	“Marketing Text message from +55 XXX XXX XXX”
body parameters	none
footer	none
buttons	none

To send this template message to the user, a POST request is required.

curl --location 'https://waba-v2.360dialog.io/messages' \
--header 'Content-Type: application/json' \
--header 'D360-API-KEY: <token>' \
--data '{
    "messaging_product": "whatsapp",
    "recipient_type": "individual",
    "to": "<<RECIPIENT_PHONE_NUMBER>>", //phone number with prefix
    "type": "template",
    "template": {
        "name": "marketing_text_no_param", //template name
        "language": {
            "policy": "deterministic",
            "code": "en"
        }
    }
}'

Response

An usual response is expected after a successful message sent using Cloud API.

200

{
    "messaging_product": "whatsapp",
    "contacts": [
        {
            "input": "<phone number>",
            "wa_id": "<<waba id>"
        }
    ],
    "messages": [
        {
            "id": "wamid.HBgLNTk4OTQ3MTQ0NjMVAgARGBI4RDkyRTdBMDY0QURDNEZBNUMA",
            "message_status": "accepted"
        }
    ]
}

You should expect the following Webhook notifications to be received after a successful message received and read by the user:

• Message Sent Webhook Notification

• Message Delivered Webhook Notification

• Message Read Webhook Notification

Comparison between sending a Marketing Template message using Cloud API vs MM Lite

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 the same Marketing Template Message as we did in the previous step (1.d), only the URL must be changed. The body content of the message should remain.

Cloud API	MM Lite Alpha	MM Lite Beta
https://waba-v2.360dialog.io/messages	https://alpha-beta-onboarding-hub-production.360dialog.io/mmlite/marketing_messages	https://waba-v2.360dialog.io/marketing_messages Not available yet.

For details on the template body, you can check the Cloud API documentation, as the MM Lite API uses the same API payload syntax and requires the same permissions.

MM Lite Alpha

curl --location 'https://alpha-beta-onboarding-hub-production.360dialog.io/mmlite/marketing_messages' \
--header 'Content-Type: application/json' \
--header 'D360-API-KEY: <token>' \
--data '{
  "messaging_product": "whatsapp",
  "recipient_type": "individual",
  "to": "<number>",
  "type": "template",
  "template": {
    "name": "marketing_text_no_param",
    "language": {
      "policy": "deterministic",
      "code": "en"
    }
  }
}'

Cloud API

curl --location 'https://waba-v2.360dialog.io/messages' \
--header 'Content-Type: application/json' \
--header 'D360-API-KEY: <token>' \
--data '{
  "messaging_product": "whatsapp",
  "recipient_type": "individual",
  "to": "<number>",
  "type": "template",
  "template": {
    "name": "marketing_text_no_param",
    "language": {
      "policy": "deterministic",
      "code": "en"
    }
  }
}'

[optional]: 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.

2. Sending the first MM Lite Marketing Message

a. Sending a Marketing Template Message using MM Lite API

To send this template message to the user, a POST request is required.

POSThttps://alpha-beta-onboarding.hub-production.360dialog.io/mmlite/marketing_messages

Headers

Name	Value	Description
Content-Type	application/json
D360-API-KEY	Bearer <token>	D360-API-KEY received after approval to participate in this program

Body

Field	Required	Description
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)

curl --location 'https://alpha-beta-onboarding.hub-production.360dialog.io/mmlite/marketing_messages' \
--header 'Content-Type: application/json' \
--header 'D360-API-KEY: <token>' \
--data '{
    "messaging_product": "whatsapp",
    "recipient_type": "individual",
    "to": "<<RECIPIENT_PHONE_NUMBER>>",
    "type": "template",
    "template": {
        "name": "marketing_text_no_param",
        "language": {
            "policy": "deterministic",
            "code": "en"
        }
    },
    "message_activity_sharing":true
}'

Response

An usual Cloud API response is expected after a successful message sent using MM Lite API.

200

{
    "messaging_product": "whatsapp",
    "contacts": [
        {
            "input": "<phone number>",
            "wa_id": "<<waba id>"
        }
    ],
    "messages": [
        {
            "id": "wamid.HBgLNTk4OTQ3MTQ0NjMVAgARGBJDNjM1NUM2OEEyMDU4REZERTgA"
        }
    ]
}

b. Sending a Marketing Template Message with TTL 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.

What is Time-To-Live (TTL) for Marketing template messages?

If Meta is unable to deliver a message to a WhatsApp user, they will continue attempting to deliver the message for a period of time known as a time-to-live (TTL), or message validity period.

TTL is available for Authentication and Utility template messages on Cloud API, but TTL for Marketing template messages is exclusively available on Marketing Messages Lite API.

See our documentation on How to set a TTLs for Marketing template messages.

c. Creating new Marketing Templates

For Sandbox testing, marketing templates can be created only via 360dialog API.

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.

Learn more about this limitation here: https://developers.facebook.com/docs/whatsapp/marketing-messages-lite-api/support

3. Expected Errors

To understand the expected errors for MM Lite Alpha Sandbox, check our documentation:

Expected Erros & Programming Languages

4. Examples using multiple programming languages

Find our Postman Collection, NodeJS and Python references in the page below:

Expected Erros & Programming Languages