Onboard client WhatsApp accounts with a Meta Multi-Partner Solution

This guide shows you how to set up a Meta Multi-Partner Solution with Sent, onboard your clients' WhatsApp Business Accounts (WABAs) into it, and send from each one through its own Sender Profile.

A Multi-Partner Solution is Meta's arrangement for two partners serving the same WhatsApp clients. You are the Tech Provider: you own the Meta app and the client relationship. Sent is the Solution Partner and sends messages on your behalf. A client shares their account into the partnership once, and from then on Sent sends from it and obtains the access token for it. You never handle a client's token.

When to use a partner solution

Before Sender Profiles are enabled, the Sender Profiles page offers two ways to start:

You don't have to choose one or the other. A partnership doesn't stop any profile from connecting a dedicated account, and you can create a partnership later from the Sender Profiles page.

Before you start

• An organization account. A partnership belongs to your organization, never to a single profile, and the accounts in it are attached to profiles.
• The Owner or Admin role in that organization. The controls that create the partnership and onboard clients are hidden from other roles.
• A Meta app you own. Sent creates the partnership on that app, and you sign in with the Meta account that owns it.
• To attach accounts to profiles: Sender Profiles enabled, and your organization's own WhatsApp Business Account connected to Sent. Sent finds your clients' shared accounts through your organization's account, so without it none can be listed or attached. Connect it with Connect a WhatsApp Business Account. Neither is needed to create the partnership or onboard clients.

Set up the partnership and onboard clients

Attach a shared account through the API

Connect a shared account to an existing profile with POST /v3/channels/whatsapp. Use an organization API key and send x-profile-id for the profile that should send from the account, or use that profile's own API key:

curl -X POST "https://api.sent.dm/v3/channels/whatsapp" \
  -H "x-api-key: $ORG_API_KEY" \
  -H "x-profile-id: $PROFILE_ID" \
  -H "Content-Type: application/json" \
  -d '{
    "waba_id": "123456789012345",
    "phone_number_id": "987654321098765"
  }'

• waba_id is required. Take it from Client onboarded in the dashboard. The API has no endpoint that lists your shared accounts; the dashboard's Use a shared account list shows them.
• phone_number_id is optional. You can omit it to connect the account now, then call the endpoint again with the same waba_id and a phone_number_id to name the number.
• Don't send access_token, solution_id or owner_business_id; they're ignored. Sent works all three out from your partnership. The token is issued for each client business and rotates roughly every sixty days, so a token you sent would soon go stale.

The response is the WhatsApp account: waba_id, phone_number_id, solution_id, owner_business_id, status, and a reason_code and reason whenever status isn't ACTIVE. It never returns the token.

This endpoint doesn't check the number with Meta. A phone_number_id that isn't on the account still reads ACTIVE, and the profile's WhatsApp messages then fail when sent. Copy the ID carefully, or attach from the dashboard, which only offers the account's own numbers.

To attach an account while you create the profile, pass the same two fields as channels.whatsapp on POST /v3/sender-profiles. Sent fills in the solution, business, and token the same way. Creating a profile also checks the account and number with Meta, and refuses with 409 an account or number already recorded on any other profile or on an organization. A profile with its own WhatsApp account also needs a sender of its own, so channels.whatsapp requires channels.sms. See Create and activate Sender Profiles via the API.

Confirm the account can send

Read the profile's WhatsApp channel with GET /v3/channels, sending x-profile-id for the profile. Managing channels explains the full response.

Tokens, and when a client leaves

You don't manage tokens. Sent obtains each client's token when the account is attached. If Meta rejects the token while a message is being sent, Sent obtains a new one and retries the message. If Meta won't issue a new one, the message fails with reason code DELIVERY_009. Contact support if you see it.

When the relationship ends in Meta, Sent stops using WhatsApp for the affected senders.

• If a client removes the partnership from their WhatsApp account, this applies to every profile that sends from that account.
• If Meta deactivates or rejects the partnership itself, it applies to every profile attached through it and to your organization's own account.

Your organization's own account is included in the second case even though you connected it with Log in with Meta, because the partnership belongs to it. Sender Profiles on dedicated accounts aren't affected in either case. A message that lets Sent pick the channel goes out on another available channel instead of WhatsApp. Contact support to restore WhatsApp.

Removing an account is not self-service. To detach a shared account from a profile, or move a client off your partnership, contact support.

Troubleshooting

Related

• Connect a WhatsApp Business Account: dedicated accounts, and your organization's own
• Managing channels: reading WhatsApp channel status
• Multi-tenant architectures: choosing a tenant model
• Create and activate Sender Profiles via the API: channels.whatsapp at create time