WhatsApp Usernames now supported in Twilio Platform and Messaging APIs
Twilio now supports WhatsApp Usernames, which allow users to adopt optional usernames that mask their phone numbers and interact with businesses via Business Scoped User IDs (BSUID). This identifier is exposed in message webhooks and Event Streams.
WhatsApp Usernames is now supported on the Twilio Platform and Messaging APIs for WhatsApp. WhatsApp now allows users to adopt usernames. A username can optionally mask a user's personal phone number and allows them to interact with businesses through Business Scoped User IDs (BSUID). Twilio exposes this identifier in message webhooks and in Event Streams event data. Meta is releasing this functionality in multiple waves, starting on July 7, with additional countries to follow at later dates. Please check our documentation for the latest rollout schedule.
Source: original entry ↗
More from Twilio
Follow Twilio to get its new changes in your feed and email digest.
Voice Integrity now supports all three major US networks
Voice Integrity, part of Twilio's Voice Trust offering, now supports all three major US carrier networks. Businesses can register their details and outbound phone numbers directly with carriers to help identify legitimate traffic and reduce spam blocking.
Unified Login for SendGrid Marketplace Customers
SendGrid marketplace customers can now create individual Twilio logins for each user, enabling granular permission management instead of shared admin access. This rollout applies to all marketplace integrations including Azure, Google Cloud, Heroku, and AWS.
Webhook Configuration API is now Generally Available
The Webhook Configuration API enables customers to configure authentication and delivery settings for outbound webhooks on a per-URL basis through Webhook Settings and Webhook Rules resources.