What's new?

TicketingDocumentServicesRQ has been through many revisions since 2014 and has had numerous enhancements and fixes. See Release Notes for details. 
Operations supported within TicketingDocumentServicesRQ API: 

• GetTicketingDocumentRQ 
• UpdateTicketingDocumentRQ 
• UpdateServiceCouponRQ 

Description of changes from 3.3.0 – 3.4.0: 

• Addition of Date and Time information to better indicate details of when Exchange transaction occurred 
• Addition of information of EMD document such as the itinerary was Domestic, The company or airline who is presented with a service coupon by the customer 

Schema changes from version 3.3.0 to 3.4.0: 

• Added optional use TimeForPricing attribute to the Ticket/Details/LocalIssueDateTime element that indicates the time part of the date/time 
• Added optional ExchangeTransactionDate and ExchangeTransactionTime elements in Ticket/Details/ 
• Added optional element IssueTime in Ticket/RelatedDocuments/Original/ 
• Added optional elements DynamicCurrencyConversion and TransactionId to the Ticket/RelatedDocument/Original 
• Added optional element DynamicCurrencyConversion to the Ticket/Payment/Card 
• Added optional element ItineraryType to the ElectronicMiscDocument/Details 
• Added optional elements PresentTo, PresentAt and Other to the ElectronicMiscDocument/Remark 

Description of changes from 3.4.0 – 3.5.0: 

• Expanded element length to support Corporate ID and OB Fee description 
• Added ability to support Account code and Government status on the ticket 

Schema changes from v3.4.0 – v3.5.0:

• added optional @historical indicator in GetTicketingDocumentRS/Details/ElectronicMiscDocument/Indicators/ to indicate the document is moved to historical database 
• changed GetTicketingDocumentRS/Details/Ticket/Details/CorporateId element max length from 10 to 20, updated annotations 
• added GetTicketingDocumentRS/Details/Ticket/Details/AccountCode element 
• added GetTicketingDocumentRS/Details/Ticket/Details/GovernmentStatus element with its attribute and sub elements
• added optional attribute @paymentConfirmation in Payment and RelatedDocument/Original elements of all document types in Detail and CustomDetail response typesUpdated element GetTicketingDocumentRS/Details/MiscellaneousDocument/ServiceCoupon/StartLocation from mandatory to optional.
• Updated element GetTicketingDocumentRS/Details/MiscellaneousDocument/ServiceCoupon/EndLocation from mandatory to optional.
• Updated length of GetTicketingDocumentRS/Details/Ticket/Amounts/Other/OBFee/Description from 21 to 40.

Description of changes 3.5.0 – 3.5.1:

• New operation to facilitate updating of Ticket remarks
• New elements to support the carry over of a non-refundable amount when tickets are exchanged multiple times

Schema changes from version 3.5.0 to 3.5.1:

• Added new operation: UpdateTicketingDocumentRQ/UpdateTicketingDocumentRS
• New types: UpdateDocumentTypeChoice.CG, UpdateDocumentResultTypeChoice.CG, UpdateTicketingDocumentRQ, UpdateTicketingDocumentRS, Ticketing.UpdateDocument.UpdateRemarks, Ticketing.UpdateDocument.UpdateRemarks.RS, TicketingDocumentInfo.UpdateDocument, TicketingDocumentInfo.UpdateDocument.RS, UpdateDocument.UpdateRemarks, UpdateDocument.UpdateRemarks.RS, UpdateRemarks.Remarks, UpdateRemarks.RemarksText, Remark.DetailsWithType.Set, Remark.DetailsWithType.Remove
• Added new optional element NonRefundable in GetTicketingDocumentRS/Details/Ticket/Amounts/Other/ and GetTicketingDocumentRS/CustomDetails/Ticket/Amounts/Other/
• Added 3 new types for handling extended amount value: _amountExtended, AmountExtended, AmountExtended.Details

How to migrate from previous versions?

In order to use the latest version in Production, change the version number in the TicketingDocumentServiceRQ that you are currently using to 3.27.1 since it is backward compatible with prior versions.
In the sample requests below, we considered a customer using version 3.5.1 or lower, and is now migrating to 3.27.1 to perform different operations in TicketingDocumentServiceRQ. Also, please note that, this is not a complete documentation of the elements that are present in the latest version. Developers must refer to Sabre Dev Studio for the most complete information.

GetTicketingDocumentRQ

GetTicketingDocumentRQ 3.27.1 is backward compatible with previous versions. Therefore, migration from 3.5.1 and prior versions means only updating version tag in the SOAP request (highlighted in yellow below) to 3.27.1: