Zuora Alumni

API Changelog

          • This changelog outlines the latest REST API updates and documentation updates in the API Reference: Billing. The API changes are compliant with Zuora API Policy. We would love to hear your feedback on how we can improve it. If you have any comments on the API Changelog, please send an e-mail to docs@zuora.com. Thank you!

          •  

            2021-01-21

             

          • API Updates

             

          • This section lists operations and fields that were added, changed, or removed.

             

          • The following API updates are available as of Zuora Billing Release 291, January 2021.

          •  

            • Payments - Made the following updates:

              • Changed the behavior of each of the following operations. When the Invoice Settlement feature is enabled, you can now use these operations to create or update payments.
                • CRUD: Create payment
                • CRUD: Update payment
              • In the request body of the "CRUD: Create payment" operation, changed the behavior of the following fields:
                • AppliedCreditBalanceAmount
                • Status
              • In the request body of the "CRUD: Update payment" operation, changed the behavior of the Status field.
              • In the response body of the "CRUD: Get payment" operation, changed the behavior of the following fields:
                • AppliedCreditBalanceAmount
                • Status
            • Refunds - Made the following updates:

              • Changed the behavior of each of the following operations. When the Invoice Settlement feature is enabled, you can now use these operation to refund payments.
                • CRUD: Create refund
                • CRUD: Update refund
              • In the request body of the "CRUD: Create refund" operation, changed the behavior of the SourceType field.

             

          • Doc Updates

             

          • This section lists the documentation updates that were made in this version of the API Reference.

          •  

            • In the "Subscribe" action, updated the description for the action and the description of the subscribes > SubscriptionData > RatePlanData > RatePlanChargeData > RatePlanCharge > TriggerEvent field in the request body to indicate when previewing invoices with this action, the corresponding Contract Effective, Service Activation, or Customer Acceptance date is required if the subscription contains a charge with its trigger event being set as ContractEffectiveDate, ServiceActivationDate, or CustomerAcceptanceDate.
Tags (1)