Overview

• New OrderCreate version for 17.2, which will be V3, the URL that agents call will be the same just with V3 at the end rather than V1 or V2. (See URL Service Endpoint below) 
• No changes to Mashery plans, any agent who has access to 17.2 V1 or V2 will have access to V3
• No functional changes to the internal works on the service, they’ll be able to create the same bookings and access the same functionality they can on V2
• If there is any data missing in the response that agents wish to use then they are able to immediately call OrderRetrieve to get that data
• Users should see a speed increase which scales with the complexity of the booking, so the more passengers/segments/ancillaries in the booking the better the improvement will be
• The number we’re touting internally is 10 seconds but this is an average, some booking may have more than 10 second savings, and some may have less. I’d suggest not giving any figures on possible time savings

What differences will there be in the schema?

The following elements are present in the current OrderViewRS, but will not be present in the new V3 version

• /OrderViewRS/Response/Order/OrderItems/OrderItem/PriceDetail/Taxes/Breakdown
• /OrderViewRS/Response/Order/OrderItems/OrderItem/Penalty
• /OrderViewRS/Response/TicketDocInfos/TicketDocInfo/TicketDocument/CouponInfo
• /OrderViewRS/Response/DataLists/ContactList
• /OrderViewRS/Response/DataLists/BaggageAllowanceList
• /OrderViewRS/Response/DataLists/DisclosureList
• /OrderViewRS/Response/DataLists/PenaltyList
• /OrderViewRS/Response/Metadata

URL Service Endpoint

amples