Skip Navigation

Get Electronic Document

2.2.0
Air
Ticketing
SOAP API
Travel Agency

v2.2.0 | January 12, 2023

  • Added parameters for passenger type used to issue the ticket and translated passenger type code.
Read more

API Information

Format
XML
Current Version
2.2.0
Environment
Production

What's New

  • Added parameters for passenger type used to issue the ticket and translated passenger type code.

New Features

In the Response

Optional

Parameter: GetElectronicDocumentRS/DocumentDetailsDisplay/Ticket /Customer/PassengerType

Type: string

Description: The passenger type used to issue the ticket

Sample Value:

A
Note: A = Adult (ADT) C = Child(CNN) IN = Infant (INF) N = Military (MIL) UM = Unaccompanied Minor (UNN)

In the Request

Optional

Parameter: GetElectronicDocumentRS/DocumentDetailsDisplay/Ticket /Customer/PassengerTypeDecodedValue

Type: string

Description: This is the translated passenger type code (from used to issue the ticket

Sample Value:

ADT
Note: ADT=Adult CNN=Child INF=Infant MIL=Military UNN=Unaccompanied Minor

v2.0.0 | January 27, 2022

  • In this version new functionality was introduced.
Read more

API Information

Format
XML
Current Version
2.0.0
Environment
Production

What's New

  • In this version new functionality was introduced.

New Features

In the Response

Optional

Parameter: StopOver

Type: string

Description: A code to indicate whether the passenger is entitled to make a stopover at the fare paid

Sample Value:

O = Stopover permitted
X = Stopover not permitted
Note: This new element will contain the stop over indicator and is flagged at the coupon level. When a stopover is flagged then the field will be present and will contain one of the following values:- O = Stopover permitted X = Stopover not permitted When the stopover indicator is “blank” or not returned by the carrier then this field will not be created.

In the Response

Optional

Parameter: StartDate

Type: date

Description: The flight departure date or the start date when the service is applied

Sample Value:

2017-10-25
Note: The start date of the flight coupon. If there is no flight date, for example the journey is open, then this field will not be returned

In the Response

Optional

Parameter: StartTime

Type: time

Description: The flight departure time or the start time when the service is applied

Sample Value:

20:00:00
Note: The start time of the flight coupon. If there is no flight time, for example the journey is open, then this field will not be returned.

In the Response

Optional

Parameter: CurrentStatusCodeSetValue

Type: string

Description: A 1 to 3 character IATA padis codeSet(4405) value for coupon current status

Sample Value:

I
Note: This element will return the EDIFACT coupon status as returned by the carrier. Note : - this data element is translated to the descriptive status present in the <CurrentStatus> field.

v1.0.0 | May 18, 2018

  • The Get Electronic Document service can be used to display an ETR or EMD that is issued by a Sabre Travel Network subscriber’s PCC or authorized branch. The document must be accessible in the carrier’s database. Requests for documents that have been purged in a carrier’s system will fail, even if the data is still available in the Sabre database via a WTDB request.
  • Sabre system validations will determine if the requestor is entitled to view a specified document and send an EDIFACT display request to verify that the document is present in the validating carrier’s electronic document database. System processing will translate the carrier’s EDIFACT response to XML and return those data elements that are currently viewable in the Sabre green screen displays (WETR*, WETR*/E, WEMD*).
  • Subscribers must provide their own application program to display the service response.
Read more

API Information

Format
XML
Current Version
1.0.0
Environment
Production

What's New

  • The Get Electronic Document service can be used to display an ETR or EMD that is issued by a Sabre Travel Network subscriber’s PCC or authorized branch. The document must be accessible in the carrier’s database. Requests for documents that have been purged in a carrier’s system will fail, even if the data is still available in the Sabre database via a WTDB request.
  • Sabre system validations will determine if the requestor is entitled to view a specified document and send an EDIFACT display request to verify that the document is present in the validating carrier’s electronic document database. System processing will translate the carrier’s EDIFACT response to XML and return those data elements that are currently viewable in the Sabre green screen displays (WETR*, WETR*/E, WEMD*).
  • Subscribers must provide their own application program to display the service response.