This article will help you in understanding the technical updates happening to gupshup.io or partner.gupshup.io services.
Jan 2025
-
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. -
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. -
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.
-
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.
- 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. -
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.
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 soon, we request you that you start using the subscription API, as it provides you with a granular control for event management on your callback URL
Deprecation Timeline : Yet to be announced
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.
- 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 - 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 - 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 - 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
- For existing subscriptions or Callback URLs set : Gupshup will handle the switch for you for existing set modes
COMING SOON
- Template Matching Service - Not Recommended:
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 -
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 soon. Thus, we request you to start doing the changes in your integrations immediately. - Synchronous Responses No Longer Supported:
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. - Subscription Changes
Thank you for your cooperation and understanding. If you have any questions or need assistance, please don’t hesitate to reach out to us.
Comments
0 comments
Please sign in to leave a comment.