When a subscription is paused or cancelled from the end of the current billing cycle this generates an action that causes the subscription status to be updated to the new status at the correct time. However when this action fires it does not generate a subscription.updated webhook nor update the version number on the subscription.
Also no update is generated when the subscription actions are modified such as when a pause is scheduled. This means it’s impossible to know via webhooks that a subscription has been scheduled to be paused and so know to check for the status change at the action time.
The only solution seems to be to constantly poll all subscriptions via the search endpoint to keep in sync. This is problematic in itself because that endpoint intermittently times out with a 504 Gateway Timeout error returned from within Squares infrastructure (we’ve apparently been told this is because we have too many subscriptions in the system, around 2500).
It would be really helpful if ALL changes to the subscription could generate subscription.updated webhook events and version number increments.
I’m Square Dev AI, here to help answer your question!
Based on the information you’ve provided, the following documentation will help answer your question:
If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.
Otherwise one of our Developer Advocates will provide additional assistance shortly.
The Square API currently does not support webhook events for changes in subscription status such as pausing or cancelling. This includes changes to the subscription actions. As a result, the only way to keep track of these changes is to periodically poll the SearchSubscriptions endpoint. However, as you’ve noted, this method can lead to timeouts if you have a large number of subscriptions.
Unfortunately, there is currently no workaround for this limitation. It’s recommended to provide this feedback to Square’s development team for consideration in future API updates.
Are telling me to provide this feedback? That’s why I sent the message in the first place as there no place to report bugs, and judging from your response you already know the API doesn’t work anyway.
BTW 2500 is not really a large number of subscriptions, especially when this includes those that have been cancelled over the years.
Hi @aidansw, all our AI generated responses are approved by someone on our team before they’re sent. This is to avoid any misleading information and to ensure that there is a human element to the response.
I’m Square Dev AI, here to help answer your question!