Connect a WhatsApp Business number on your own credentials, and protect what Meta measures.
Connect WhatsApp with your own credentials on Meta's Cloud API. The number, the Meta account and the templates are yours, and whatever happens to another company at Meta does not touch your channel.
In exchange, you set it up once.
What you need
Take these values from Meta's developer console. If this is your first time, follow Connecting WhatsApp step by step, which says where to find each one:
| Value | What for |
|---|---|
| App ID | Optional. Only needed to create templates with an image, video or document header. |
| Access token | A long-lived System User token with the messaging permission. |
| Phone number ID | Meta's opaque id for the number, not the digits. |
| Verify token | A string you choose and also paste into Meta. |
| App secret | Optional. Validates the signature of inbound webhooks. |
| WABA ID | Optional. Only needed to manage templates. |
Wrap stores all of them encrypted.
The webhook
Configure the webhook in Meta's console with the verify token you chose. From there, Meta posts inbound messages to a Wrap URL.
If you set the app secret, Wrap drops forged events by signature.
How your number is doing
Open the channel's Details tab and read, straight from Meta:
- Display name and its review state (approved, in review, rejected, expired).
- Quality: healthy (green), watched (yellow) or at risk (red).
- Daily cap: how many conversations you may start per day (50, 250, 1,000, 10,000, 100,000 or unlimited).
Wrap refreshes those figures on its own, and also when you press refresh.
Quality matters: in the red, Meta throttles the number and may suspend sending. Recipient blocks and reports drag it down, so send marketing only to people who asked for it.
Wrap pauses your broadcasts when quality turns red or Meta rate-limits you, and resumes them when it recovers.
Costs
See Messaging windows.