API subscription Cancellation (DELETE) Request Changes

As of July 6, 2018, we have modified the subscription cancellation request endpoint/response. Previously, calling the DELETE method on a subscription that has already been canceled would return a 200 response (provided all other parameters were correct) and the subscription would simply remain canceled.

With the changes that we have made, calling the DELETE method on an already canceled subscription (provided all other parameters are correct) will now return a 422 (unprocessable entity) response and include the error message ‘The subscription is already canceled’.

This was modified to:

  1. Limit duplicate calls to the API
  2. Better handle situations where attempting to cancel_at_end_of_period a Subscription that has already been canceled returned an uninformative response. Previously such a call would return a 200 response and users wouldn’t be aware that the subscription in question was already canceled. This change remediates that issue by returning an informative response.