Sending Active Messages with BSUID

Coming soon!

⚠️ The behaviors below represent the current design of the functionality and may evolve until the final release.

Index

1. What DOES NOT change
2. What evolves
   1. Growth - Individual sending
   2. Growth - Bulk sending (CSV)
   3. Desk - Sending messages with BSUID
   4. Evolution of API payloads - Growth
   5. GET /accounts
3. Broadcast plugin

What does not change

• Active sends via phone number continue to work normally
• Active message templates continue to work

• The option to send active messages via API (Growth and Blip) remains available

   

What evolves

Blip Portal - Growth Individual

The individual sending interface will offer the option to send by:

• Phone Number (current model)
• BSUID (new)

Blip Portal - Growth Bulk (CSV)

The first column of the CSV file will accept both types of values, including mixed in the same dataset:

The column name does not need to be changed. Mixed audiences (PN and BSUID interleaved) are supported.

⚠️ Attention! If PN and BSUID of the same user are present simultaneously in the dataset, 2 sends will be made to the same user. Ensuring deduplication is the sender's responsibility.

Desk - Sending messages by BSUID

Sending active messages via Desk will allow searching by BSUID ("equals" filter). The contact display during the sending flow will also show username and BSUID.

Evolution of API payloads - Growth (Active Campaign)

Field recipient

The recipient field (contact identifier without domain) will accept PN (already supported) and BSUID (new option).

Impacted endpoints: POST /campaign/full and GET /audiences/v2/{{id}}

POST /campaign/full - Sample payload

GET /audiences/v2/{{id}} - Sample payload

Under review for future evolutions: support for Blip ID (GUID) and Parent ID as recipient.

Field recipientIdentity — /campaigns/summaries

Currently always returns {phone}@wa.gw.msging.net. After the update, it may return PN or GUID.

Field validatedAccount — /audiences

Currently always returns {phonenumber}@wa.gw.msging.net. After the update, it may return PN or GUID.

GET /accounts

The GET /accounts endpoint will accept BSUID as a query parameter (in addition to PN). The to field of the sending payload does not change; it will continue to be filled with the identity obtained via GET /accounts.

BEFORE - Sample payload

AFTER: PN as contact ID - Sample payload

AFTER: GUID as contact ID - Sample payload

Broadcast Plugin

⚠️ The Broadcast Plugin does not follow the evolution of WhatsApp's identity model and there is no forecast for adaptation to support usernames, BSUIDs, and the new contact creation logic implemented in Blip.

A gradual migration to Blip's Growth API is recommended. Keeping the plugin may result in duplicate contact creation, history fragmentation, and loss of continuity in scenarios with new IDs.

Need more help? Explore our content at Blip Academy or Blip Community, watch tutorials on our YouTube channel, or ask your questions in our support channel 😃