XML Samples

For more efficient maintenance, samples do not indicate the Universal API release or the schema version in the file name. Version control for samples uses:

• The schema versions are indicated in the namespace for each sample request and response. For example:
  <air:AirPriceRsp xmlns:air="http://www.travelport.com/schema/air_v50_0" xmlns:common_v50_0="http://www.travelport.com/schema/common_v50_0">
• Comments at the top of each sample request indicate:

• The associated release.
• A brief description of the transaction.
• A date stamp for the date when the sample was generated. If a sample is modified in the same release, the date stamp can be used to confirm the exact date of creation for the sample. For example:

<!-- Release 6.0-->

<!-- Timestamp: 23 Nov 2013-->

<!-- Air Booking For Galileo(1G) with Connection Request-->

• Date stamps are also included:

• In eachdescription on the Sample topic page as Created or Updated. Any updates from the initially created sample are listed in a corresponding pop-up box.
• On the All Sample Files Zip file name to indicate the latest date that an update was made to a sample contained in the Zip.

For sample transaction requests, values for credentials, credit cards, and other sensitive data are replaced with generic equivalents. When testing with sample requests, please replace:

• OriginApplication="UAPI" with your assigned OriginApplication, if applicable. If you have not been assigned another OriginApplication value, retain the "UAPI" value.
• TargetBranch=“TRGT_BRCH” with your assigned Target Branch/Work Area Branch (WAB).
• PseudoCityCode=“PCC” with your assigned pseudo city code.
• CreditCard @Name @Number @CVV with your own test credit card data.

Other values that are not validated by Universal API, such as LoyaltyCard @CardNumber, may be kept or replaced with your own test data.