Migrating From the SOAP API

Knowledge Center > Subscriptions > Orders > Orders Tutorials > Cancel a Subscription > Migrating From the SOAP API

Migrating From the SOAP API

When the Orders feature is enabled, the subscribe() and amend() calls are not available. Additionally, the create(), query(), delete(), and update() calls are disabled for amendments. You must migrate any SOAP integrations using these SOAP calls to use the REST API instead.

To assist with the migration, this article provides the SOAP equivalent of the "Create and activate order" request body shown in Cancel a Subscription.

SOAP Example

The following SOAP amend() example is valid for WSDL version 29.0 and later.

         <obj:Name>Cancel a subscription</obj:Name>       
         <obj:Description>Cancel a subscription</obj:Description>    

Migration Notes

  • Specify account numbers instead of account IDs.
  • Specify subscription numbers instead of subscription IDs.
  • Specify the type to CancelSubscription instead of Cancellation.
  • The effective date specified in the SOAP EffectiveDate field corresponds to the cancellation effective date of the order action in the REST API.
  • You do not need to specify the status of the amendment in the REST API. Because the amendment will be in the Complete status if the call succeeds. You cannot create draft amendments in Orders.
  • To generate invoices and collect payments, specify the runBilling and collectPayment fields instead of the GenerateInvoice and ProcessPayments SOAP fields.
  • Currently, we do not support specifying the name and description of order actions (the corresponding Name and Description SOAP fields).
Last modified


This page has no custom tags.


(not set)