Infobip WhatsApp BSUID Compatibility

Infobip WhatsApp Business API BSUID migration guide. Learn how to handle the new user_id parameter in inbound message events for username-initiated conversations.

Infobip BSUID compatibility card

Infobip API Updates for WhatsApp Usernames

Infobip users utilizing the WhatsApp Cloud API will notice a new user_id parameter flowing through their inbound message events starting in Q3 2026. This parameter carries the Business Scoped User ID (BSUID) when customers initiate contact via a WhatsApp username.

What Is the user_id Field?

The user_id field is an opaque, alphanumeric identifier that represents a unique user within your WhatsApp Business Account scope. It replaces the traditional phone number as the primary identifier for users who contact you via username.

Infobip Webhook Payload Changes

Legacy payload: {"results":[{"from":"1234567890","text":"Hello"}]}

New payload: {"results":[{"from":"BSUID.a1b2c3d4e5f6","user_id":"a1b2c3d4e5f6","text":"Hello"}]}

Migration Checklist

  1. Update your Infobip webhook endpoint to capture the user_id field
  2. Modify your CRM schema to store BSUIDs alongside existing phone number records
  3. Implement fallback logic: use from if user_id is absent (legacy conversations)
  4. Run end-to-end tests with Infobip's sandbox environment

Timeline

Infobip will support dual-mode (phone number + BSUID) through Q3 2026. Starting Q4 2026, new username-initiated conversations will carry BSUIDs exclusively.