Time to live support in User initiated calling template and session messages

You can now set time-to-live for user initiated calling relating messaging CTAs.

Waba Health API now provides Meta phone number ID

You can now get Meta phone number ID in the waba health API along with app ID.

Phase 1 - Support for Usernames / BSUID is now ready

In the first phase, we are introducing optional support for BSUIDs with minimal disruption:

No default changes
Your current setup will continue to work as-is. Messaging via phone numbers (v2 and v3) remains unchanged.
Optional BSUID enablement (App-level flag)

Partners can choose to enable a flag to receive BSUID-related data (such as username, BSUID, etc.) along with phone numbers in:

Incoming messages
Delivery reports (DLRs)

Meta Timeline – Quick Recap

Early April 2026 (starting ~6th April)
BSUIDs have begun appearing in webhooks alongside phone numbers (gradual rollout). The date previously as 31st March had moved to 6th April.
May 2026 APIs will support sending messages using BSUID instead of phone numbers (Phone number-based messaging will continue to work) June 2026 (or later)
Limited rollout of end-user usernames in WhatsApp H2 2026 Broader rollout of:
- End-user username adoption
- Business username adoption

Partners who wish to start using BSUID can opt-in once the updated documentation is released. Keep an eye on this article for further updates.

Security Enhancements : New and Upcoming

We are strengthening security and control mechanisms within the Partner Portal. Below are the key updates:

IP Whitelisting via UI Partners can now enable IP whitelisting directly from the UI of the partner portal - Activation will require: Verification of Primary Number (PN) Email OTP authentication Coordination with your Customer Success Manager (CSM) - one time

This ensures that API access (some of them) is restricted only to trusted IPs

Private Key-Based Authentication for Bulk key rotation Introduction of public/private key-based authentication for: Bulk App API Key generation Token rotation workflows This replaces less secure methods and significantly hardens API access. Setup requires: Verification of Primary Number (PN) Email OTP authentication Coordination with your Customer Success Manager (CSM) - one time

This ensures that your app API keys and app tokens can be rotated in bulk.

Secure App Linking via One-Time Token (not from gupshup.ai interface) App to partner linking will soon be done using a one-time token. Token that will be generated on the Self-Serve (SS) U must be used by partners to complete linking. This removes manual or less secure linking mechanisms
Mandatory Multi-Factor Authentication (MFA) on gupshup.ai Adds an extra layer of protection against unauthorized access
App-Level API Keys Only Account-level API keys are being deprecated for new accounts Only app-level API keys will be supported going forward
Webhook Notifications for Critical Changes Webhooks will be triggered when: Profile settings are updated Callback URLs are modified

These enhancements are part of our ongoing efforts to strengthen platform security, improve control, and ensure a safer ecosystem for all partners and customers.

Gupshup Pricing / Policy Updates

DEPRECATED : ‘Allow category change’ flag for template creation

As Meta has deprecated this feature during template application, Gupshup also does not support or pass this field to Meta any more. Hence it is recommended to not pass this field in your template creation requests.

REMINDER : Gupshup Partner Terms of Use – Action Required

The Gupshup Partner Terms of Use are available on Partner Portal. Please refer to the official link below for the Partner Terms of Use: https://www.gupshup.ai/partner-terms-of-use These terms are also available in the Partner Portal → Resources → Legal section.

Why this matters?

The partner terms of use is Gupshup's endeavor to provide you a single, always-updated source of truth, improve compliance, and ensure uninterrupted access to partner features. It thereby provides 100% clarity and transparency between Gupshup and you, thus leading to smoother collaboration going forward.

Acceptance Required for Partners We have started capturing acceptance of the terms on the Partner Portal once you login. Acceptance must be completed by a partner account admin Recommended deadline: April 30 2026 Partners who do not accept the Terms by this date may start losing access to certain partner features

We request you to review and accept the Terms within the stipulated timeline.