Gupshup Webhook Updates for BSUID
Gupshup, one of the largest WhatsApp Business Solution Providers, is rolling out BSUID support across its API platform. If you use Gupshup for WhatsApp messaging, your inbound webhook processing needs to be updated.
What Changes in the Payload
The sender field in Gupshup webhooks will now return an alphanumeric BSUID string instead of a standard international phone number when a user initiates contact via a WhatsApp username. Your existing code that parses sender as a numeric value will break.
Code Example: Safe Parsing
Instead of int(sender), use a string-based approach: str(sender).lstrip("whatsapp:"). Check for the BSUID. prefix and handle accordingly.
Recommended Actions
- Audit all webhook endpoints that parse the
senderfield - Update type casting from integer to string
- Test with sample BSUID payloads before the Q4 2026 cutoff
- Notify your engineering team about the schema change
Gupshup-Specific Notes
Gupshup passes Meta payloads with minimal transformation, so the raw BSUID format is preserved. Your handler should expect the same schema as the raw WhatsApp Cloud API with Gupshup's standard wrapper.