This action allows you to edit a Subscription. Editing a Subscription will return the updated Subscription object so you can verify your changes.
Special Considerations
Request considerations: Due to the complex nature of the subscription use a get/put methodology when modifying a subscription. If values are not included, they will usually get nullified.
Request limitations: Only the listed fields can be edited via the PUT Subscription operation. Check the subscription product update for even more details.
To change quantity or to include or un-include a plan product the manipulation must occursubscription product. This can either be as part of the subscription product list in this call, or as a separate call to update a specific subscription product.
Change subscription name/description: Enter values into the subscriptionOveride object.
Editing reference: Update the Reference field.
Editing contract start and end dates: Set UTC datetime values in the contract fields
Setting, modifying and removing the scheduled activation date: Set UTC date time value in the scheduledActivtionTimestamp field
Setting the expiry period: This can set by submitting a number for the remaining expiry periods in the remainingInterval field. The value “0” immediately expire the subscription at the end of the current cycle. This can be used to end a subscription gently and finish charging any end of period charges.
Query considerations:Disable automatically sending invoice changes and defer them to a ready draft invoice by setting the temporarilyDisableAutoPost query parameter.
secure.fusebill.com/v1/subscriptions?temporarilyDisableAutoPost=trueCharges generated in this way will be Draft and have a Ready status. The resulting invoice will not be automatically posted until a user or integrator goes out of their way and performs a Post Ready Charges. Or will be picked up with the next automatic invoice if the "Post ready on recharge" is set on a customer. More information on Draft Invoice Object
When modifying any Subscription Products Object with more than one discount, remove the subscriptionProductDiscount (legacy singular object) entity and leave subscriptionProductDiscounts (list of discounds, plural) in place in order to retain those discounts. Otherwise these will get nullified if not provided in the update payload.
Setting the PriceUpliftsEnabled on a Subscription Products Object to "False" from a previous value of "True" will delete existing, future and historical price uplifts.