1.1 Overview

The new EMD Exchange API provides Sabre Travel Network agency customers the ability to exchange one associated Electronic Miscellaneous Document (EMD-A) for another, single EMD-A.

It is the responsibility of the consuming application(s) to carry out the formatting and presentation of the data provided. Sample layouts from the Sabre host version of the solution are provided in appendix 6.1 for guidance purposes.

This EMD Exchange solution is available as an addition to the existing service. TKT_ExchangeRefundRQ API (version 1.4.0 and higher), as a new operation element, ExchangeEmdRQ.

Note: Sabre Airline Solutions customers should continue using the existing API, ExchangeDocumentforEMDRQ, to process airline EMD exchange transactions.

1.2 Purpose of this Guide

The purpose of this guide is to introduce how the API processes EMD-A Exchange requests.  It is not a complete documentation of XML design. The Sabre repository for all API information can be found at Sabre Dev Studio. Please visit the register for an account if you have not done so already.

This introductory guide provides:

• Description of API features
• Examples of typical EMD Exchange requests and responses
  • EMD Exchange calculation summary
  • EMD Exchange fulfillment
• Common error messages that may be returned by the API along with the explanation as to why they occur and ways for fixing the problem where applicable.

It is assumed that a developer implementing ExchangeEmdRQ has a solid understanding of the underlying Sabre functionality, or that they have access to a Sabre Subject Matter Expert at the agency.

This document does to attempt to explain the purpose/functionality of airline ancillary services, EMDs, PNR’s, electronic airline document exchange transactions, agency reporting/settlement requirements, or agency accounting processes.

1.3 Examples in this Document

The purpose of the XML examples provided in this document is to present the possible content of the request and response (RQ/RS). These examples are for illustrative purposes only and in some case may be truncated to save space – they are not always complete XML documents.

1.4 Sabre Dev Studio

Sabre Dev Studio has many resources for implementing Sabre APIs including schemas, WSDL files, TTL files, full RQ/RS XML samples, design documents, workflows, and helpful related information.

Users must have a registered account to gain access to the comprehensive references available for developers implementing Sabre APIs.

1.5 EMD Exchange WSDL and TTL Files

The API Description (WSDL) file provides a description of the basic formats of the API requests – how the service can be called, expected parameters and what data structures it returns – so you can easily get the service running on your development/testing tools.

The Ticketing Type Library (TTL) file is a library of common terms and elements that the ExchangeEmdRQ operation will reference when it is called by your client/GUI.

For the latest WSDL and TTL files, check the ExchangeEmdRQ Resources page at Sabre Dev Studio.

1.6 Getting Started Guide

For information on how to connect and create a session, please access Getting Started in Sabre Dev Studio.