Updated version of the V6 API for Orders released 3-13-19

PRESSERO > *Integration Information & Supported Services
On March 13, 2019 we released an updated version of the V6 API for Orders, the reason for this is to improve the speed of our API and reduce the amount of data returned on a single call, basically we're removing unnecessary information from some levels of the payload, the information will all be available in other endpoints, like the Product endpoint, Site endpoint, etc.
 
Order Details (Removed Data per Property)
 
User
Groups
UserCustomProfileFields
SSOUsers
LastFailedLoginAttemp
Website
UserContactPermission
 
CheckoutSitePaymentMethod
AllowedGroups
SitePMConfigInfo
 
Payments
Added PaymentMethodName
Added PaymentServiceName

Tagged SitePaymentMethod as obsolete to be removed in April from the API
 
Order Item Details (Removed Data per Propery)
 
EDocInfo
_edocCode (Informationm is already rerturned on edocCode)
_edocSession (Informationm is already rerturned on edocSession)
 
Product
Categories
Attributes
ProductGroupCalculators
IntegratedProducts
AllowedGroups
Workflow
Added WorkflowName
 
SiteShippingMethod
AllowedGroups
Tagged SubscriberShippingMethod as obsolete to be removed in April from the API
Added MethodName
Added Carrier
Added ServiceName
 
CurrentStatus
WorkflowStage
Added PublicName
Added PrinterName
Added StageMeaning
 
Payments
Added PaymentMethodName
Added PaymentServiceName

Tagged SitePaymentMethod as obsolete to be removed in April from the API
 
OrderItemStatus
WorkflowStage
Added PublicName
Added PrinterName
Added StageMeaning
 
The information was only removed from the payload for Order Details and Order Item Details, the full information for all those items are still available in the API in their specific calls, the idea is to keep those objects as dry as possible, so for now on any information added to the Order and items should be analyzed before adding to the API, to see if they're really necessary for those endpoints.
 
To reduce the impact on customers, we also added some information that we think can reduce the number of calls the user might need to do to the API, so that’s why you will see new properties on the objects.
 
The API documentation for those affected endpoints has also been update and expanded, so the user can better understand what information will be returned on each property.