Skip to main content
When migrating to REST, it is important to note the following three key ways in which REST differs from SOAP:
  • Creating Objects in REST is done using POST. As in SOAP, the creation of multiple Objects in a single call is supported. You can POST a new account and a new payment method, and they will be created and connected.
  • Unlike SOAP, when updating Objects in REST each Object should be updated individually. For example, to update a payment method, you should use the Payment Method endpoint and this should be performed separately from any other changes. If you need to change the account name, perform the update separately.
  • In REST, Payment Method Tokenization (PMT) replaces Hosted Order Automation (HOA) Payment Method update. PMT is very similar to HOA, which means you can accept credit cards on your website securely without ever handling the sensitive information within your network. PMT uses REST to send the credit card information back to Vindicia.
  • In REST, a new policy attribute is included in the objects themselves and encapsulates the different input parameters that were added to calls in SOAP. For example, ignoreAVS input for Autobill, Transaction, or Payment Method update in SOAP is a policy attributeignore_avs_policy.
  • Soap Autobill Modify and Update are two separate calls, in REST this is combined in to a single endpoint. Therefore in REST, when modifying the Subscription’s Billing Plan or Subscription Items we cannot update other variables.
This section contains the following topics: