Skip to main content

Gupshup Technical and Policy Updates- 2025

Gupshup
Updated

This article will help you in understanding the technical updates happening to gupshup.io or partner.gupshup.io services.

 

UPCOMING END OF LIFE / CHANGES

  1. Callback URL Deprecation by July 31, 2025 :
    We are going to be deprecating this API or any other api to set callback URL by April 30 2025.
    Alternative : We request you that you adapt the     subscription API, as it provides you with a granular control for event management on your callback URL.
    You can now set subscriptions for both V2 and V3 APIs, with the flexibility to configure up to maximum five subscriptions per app.     We've also enhanced our Subscription API with multiple modes to simplify event handling and give you greater flexibility in managing real-time data such as - 

    FLOW_MESSAGE MODE 
    PAYMENTS MODE
    FAILED Mode
    BILLING Mode

  2. Any new apps created after Aug 01, 2025 will not support all the 3 services deprecated in June 2025 (mentioned below) as well as Callback URL APIs.

  3. Changes to Post-login Experience on Gupshup.io (July 2025 onwards)

    We’re also updating the post-login experience to streamline navigation and improve platform stability:

    ✅ New login redirect:
    After logging in from gupshup.io, users will now be taken to:
    https://www.apps.gupshup.io/whatsapp/dashboard
    instead of the previous URL:
    https://www.gupshup.io/whatsapp/dashboard

    ✅ Other pages like settings, templates, and wallet:
    Will similarly redirect to their apps.gupshup.io URLs.
    Example:

    https://www.gupshup.io/wallet → https://www.apps.gupshup.io/wallet

    ⚠️ Important:

    There is NO change to any API behavior, callback/subscription mechanism, or authentication nor to the partner portal.

    Partners using unofficial UI methods or UI APIs should note: your experience could break due to these changes.

     

 

JULY 2025

Meta Per Message Pricing (PMP) related changes from Gupshup side. READ HERE

 

 

 

JUNE 2025

  1. DEPRECATED - /sm endpoints - by 30th June 2025
    Note that any new apps created after Aug 01, 2025 will not support /sm endpoints.
    ALTERNATIVE : Read here
  2. DEPRECATED - Template Matching Service - Getting Deprecated from June 2025
    Note that any new apps created after Aug 01, 2025 will not support template matching service
    ALTERNATIVE : If you are sending template messages, Gupshup has consistently recommended using below endpoints to send template messages. These are Template ID APIs to send template messages with params - (Note, we do not recommend sending template messages as full body through these template APIs)
    For Partners : V2 Partner endpoints or V3 Partner endpoints
    For Customers : V2 endpoints
    We strictly advise to NOT rely on template matching service on Gupshup (for those who send templates through v2 Session Message endpoints) as this service will be deprecated. Thus, we request you to start doing the changes in your integrations immediately.
  3. DEPRECATED - Gupshup provided Opt-in Opt-out and Block User APIs and UI will be will be deprecated by 30th June 2025.
    Note that any new apps created after Aug 01, 2025 will not support Optin Optout and Block user legacy APIs.
    ALTERNATIVE : The Partner API to block user at Meta level is now available. When you block a WhatsApp user, the following happens:
    1. You can only block users that have messaged your business in the last 24 hours.
    2. There is a 64k blocklist limit
    3. The user cannot contact your business or see that you are online.
    4. Your business cannot message the user. If you do, you will encounter an error.
    5. You cannot use this API to block another WhatsApp Business.

 

MAY 2025

Synchronous Responses No Longer Supported: W.e.f May 2025
Sending responses synchronously will be deprecated soon. Developers must use the ‘Send Message’ APIs for sending messages. Ensure your systems are updated to accommodate this change.

 

Feb 2025

Transition from Callback to Subscription model

We are now transitioning from a callback-based approach to a subscription-driven model for improved handling incoming events and messages. This will allow us better scalability and flexibility. 

Notice
⚠We are going to be deprecating this API or any other api to set callback URL by April 30 2025, we request you that you adapt the subscription API, as it provides you with a granular control for event management on your callback URL

Deprecation Timeline : by July 31, 2025 :

 

New Subscription Modes introduced on self serve UI and subscription API- 
We've enhanced our Subscription API with multiple modes to simplify event handling and give you greater flexibility in managing real-time data.

  1. FLOW_MESSAGE MODE for V3 APIs: For receiving only flow-related messages.
    If you’re using the MESSAGE mode, you must switch to FLOW_MESSAGE for flow messages for new subscriptions created after 18th feb 2025 to receive flow messages/events
  2. PAYMENTS MODE for V3 APIs: For receiving only payment-related events.
    You must subscribe to PAYMENTS mode for subscriptions instead of the old OTHERS mode for new subscriptions created after 18th feb 2025 to receive payment messages/events
  3. FAILED Mode for both v2 and V3 APIs:
    - A FAILED mode is being introduced to separate failed events from other events, making it easier for you to focus on what matters. You must subscribe to FAILED mode for subscriptions instead of the old OTHERS mode for new subscriptions created after 18th feb 2025 to receive failed message events
  4. BILLING Mode for both v2 and V3 APIs: You must subscribe to BILLING mode for subscriptions for new subscriptions created after 18th feb 2025 to receive billing events
  5. For existing subscriptions or Callback URLs set : Gupshup will handle the switch for you for existing set modes

 

 

Jan 2025

  1. Removal of Free $5 Credit for Prepaid Wallets:
    Previously, prepaid wallets received $5 in free credit upon wallet/ self-serve customer ID creation. This benefit will no longer be available to new wallets/customer IDs.
  2. Up to 5 Subscriptions allowed for V2 and V3 APIs:
    Subscriptions can now be set for both V2 and V3 APIs, however, starting January 29, 2025, the number of subscriptions is limited to five per app.
    NOTE : If you currently have more than five subscriptions for a single app, please email to support with the subscriptions to be removed to ensure no disruption, at the earliest.

  3. Mandatory Callback URL for Incoming Messages and Events:

    Previously, you could view incoming messages and events in real time via the Gupshup.io self-serve sandbox interface without setting a callback URL.

    Moving forward, it will be required to configure a callback URL to receive and view incoming messages and events. These will no longer be visible on the sandbox interface starting Jan 29, 2025.

  4. Discontinuation of Placeholder Webhooks:

    Placeholder webhooks and testing webhooks will no longer be supported.

    Any existing placeholder or testing webhooks will be automatically removed from the system or will be marked as inactive.

  5. Auto-Removal of Existing Bot Linkages:
    All existing Gupshup bot linkages to your WhatsApp apps on Gupshup.io will be automatically removed and moving forward, it will not be possible to link Gupshup platform bots to your WhatsApp apps on Gupshup.io as the bot platform has been deprecated.
  6. Media Rate Limiting issues resolution and guidance :
    In light of issues caused by invalid media calls in Dec 2024 and early Jan 2025, we’d like to share a comprehensive guide to help you address and avoid disruptions. Read here 
    We have also implemented the following updates:
    a. Media Preview Temporarily Unavailable: Media preview functionality in the self-serve UI is currently unavailable. Our team is actively working to bring it back as soon as possible.
    b. Rate Limit for Invalid Media Calls: To improve system stability, a rate limit has been applied to invalid media calls. Please refer to the guide for detailed information on this update and steps to ensure compliance.

 

 

Thank you for your cooperation and understanding. If you have any questions or need assistance, please don’t hesitate to reach out to us.

Related articles

Comments

0 comments

Please sign in to leave a comment.