Closed Pass a cancellation reason via the Subscriptions API

[sven-bo]

When a customer cancels through the account dashboard, they can type a cancellation reason, and it then shows up on the subscription in the dashboard.

I cancel subscriptions programmatically via the API (POST /subscription/{id}/cancel). That endpoint only seems to accept cancel_at_end. Is there any way to also send the cancellation reason through the API so it appears on the subscription the same way the dashboard does? Or is that field only available in the dashboard right now?

Thanks,
Sven

 

[Preeti Paryani]

Hello @sven-bo,

Yes, you are correct.

Currently, the Cancel Subscription API endpoint only accepts the cancel_at_end parameter. When a subscription is canceled via the API, the system records that the subscription was canceled through the API, but there is currently no parameter available to pass a cancellation reason.

We have escalated this as a feature request to our development team. If support for passing a cancellation reason via the API is added in the future, we will be sure to update you.

Thank you for bringing this to our attention.

 

[Preeti Paryani]

Hello @sven-bo,

Thank you for your patience.

We're happy to let you know that our development team has implemented this enhancement. You can now pass a cancellation reason while canceling a subscription via the API, and it will be recorded on the subscription similarly to cancellations made through the dashboard.

Please give it a try from your end and let us know if you have any questions or need any assistance with the implementation.

Thank you for your valuable feedback and feature suggestion.

 

[sven-bo]

Thank you very much for the fast implementation.

 

[Preeti Paryani]

Hey @sven-bo,

Glad to be of help!

Since you've been a valued Pabbly customer for a long time, we'd greatly appreciate it if you could take a moment to leave us a
Google Review and share your experience with Pabbly so far. Your feedback helps us improve and assists other users in making informed decisions.

PS: We are closing this thread as the issue is resolved. Please feel free to reach out to us if you face any issues in the future.