Revision as of 12:18, 12 September 2012

Preface

SIG is a middleware web service designed to provide IBE/OTA with a unified interface to the following functions of different GDS and local CRS.

Fixed date shopping
Flex date shopping
Flight Availability
Fare Availability
Fare Rule Display
Booking & Pricing
Ticket Issue
Different forms of payment: CASH, CC, CASH+CC
Booking status & Repricing
Booking Cancellation & Ticket Void
Ticket status
Schedule Display
Fare Display

Currently SIG manages interfaces with the following systems:

Galileo
Sirena-Travel & Sirena-2.3
SITA Gabriel
Biletix Distribution System (Charter Database)

SIG is an execellent chance to IBE/OTA to avoid integration with many systems because it offers

Quick new system links. As soon as organization tasks solved
IBE/OTA developers do not need to know anything about GDS/CRS. All GDS/CRS technology concerns covered by SIG team.
IBE/OTA developers do not need to speak Russian to deal with Russian systems
No extra look/book invoices even for heavy loaded B2C projects.
Comprehensive shopping engine able to find itineraries not offered by connected GDS/CRS shopping tools
Smart price and availability caching tools

Currently SIG is being used by the following projects: biletix.ru, portbilet.ru, tutu.ru, e-ticket.ru, aviarost.ru, etc. These integrations work via SIG old API not available for new customers.

Now SIG team develops new SIG API targeted to launch its basic functions at 01.10.2012. This API described in details in other sections.

WSDL & XSD. Demo, Test, Prod systems

SIG - is SOAP server. SIG team manages three systems:

Demo System. SIG WSDL. Open to public for evaluation purposes. Currently only SIG_AirShopRQ request is available
Test System. Allocated to every customer after the contract signature
Production System. Allocated to every customer when integration completed

WSDL contains the only method SIGQuerySoap which wraps the actual XML request in sig:SIGQuery+sig:Request tags.

The XML requests and replies schemas available at SIG.xsd

This is the simple request

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sig="http://sigtest.tais.ru:8098/cgi/sirena23.cgi/SIG/">
<soapenv:Header/>
<soapenv:Body>
<sig:SIGQuery>
<sig:Request>
<?xml version="1.0" encoding="UTF-8"?>
<SIG_AirShopRQ CustomerID="TestUser">
<Itinerary>
<OriginDestination ODRef="1" To="mow" From="svx" Date="2013-03-10"/>
<OriginDestination ODRef="2" To="svx" From="mow" Date="2013-03-15"/>
</Itinerary>
<PaxTypes>
<PaxType Count="1" AgeCat="ADT" PTRef="adt0"/>
</PaxTypes>
</SIG_AirShopRQ>
</sig:Request>
</sig:SIGQuery>
</soapenv:Body>
</soapenv:Envelope>

Business cases

New Booking

Fare search

Use request SIG_AirShopRQ to search few best variants flight+price for desired trip - city pairs and departure dates are mandatory. The service will return SIG_AirShopRS sructure with list of best recommendations. Each recommendation has price and set of available flights for every segment of itinerary. The reply will contain SessionID which has to be included in all subsequent requests.

Fare selection (optional)

You can choose the recommendation using request SIG_AirShopRQ with subrequest SelectedShopOption - it will be stored within session, thus you'll be able to use it later.(we work on it)

Create PNR

Use subrequest Add of request SIG_AirBookRQ to add passengers information, passenger contact information, remarks and comments. If Step 2 was skipped the subrequest SelectedShopOption with the itinerary choice has to be included on this stage. The result of this step will be creation of PNR(Passenger Name Record of Booking File) with booked flights and fare quote in case of success, or error message. The BookingReference returned is unique ID for created PNR.(not implemented yet)

When PNR is created you can read it at any moment either within the same session or in sessionless request using received BookingReference in subrequest BookingIdentity

Ticketing

Can be done at once - use subrequests BookingIdentity, Issue and Display of request SIG_AirBookRQ to issue tickets and display itinerary receipts.(not implemented yet)

Also possible to split the ticketing (as well as all other one-step tasks) on 2 or 3 steps (the same subrequest should be used) - in this case the SessionID returned by the 1st reply has to be used in subsequent requests.

Cancellation

Use subrequests BookingIdentity and Cancel of request SIG_AirBookRQ to void tickets (within the issue day) and cancel segments.(not implemented yet)

Read PNR

Use subrequest BookingIdentity of request SIG_AirBookRQ to get all PNR data - passengers, flights, remarks etc.(not implemented yet)

Display itinerary receipt

To display itinerary receipt use subrequests BookingIdentity and Display of request SIG_AirBookRQ. (not implemented yet)

Changes

To make changes to the PNR use subrequests BookingIdentity and Modify of request SIG_AirBookRQ (not implemented yet)

Transaction reference

SIG Web Service Transaction list
Transaction	Input	Output	Implemented
Low fare search	SIG_AirShopRQ	SIG_AirShopRS	*
Create/retrieve/modify/ticket/cancel bookings	SIG_AirBookRQ	SIG_AirBookRS
Retrieve fare rule.	SIG_AirFareRuleRQ	SIG_AirFareRuleRS

SIG_AirShopRQ

Allows to search low fares for any type on itinerary - one way, round trip, closed loop or open jaw. The search might be tuned using different kind of search parameters and filters.

For detailed description see SIG Web Service data types definition and check latest WSDL at SIG Web Service Definition

One way trip for one adult passenger

<SIG_AirShopRQ CustomerID="TestUser"
<Itinerary>
<OriginDestination ODRef="1" To="mow" From="par" Date="2013-03-10"/>
</Itinerary>
<PaxTypes>
<PaxType Count="1" AgeCat="ADT" PTRef="adt0"/>
</PaxTypes>
</SIG_AirShopRQ>

Round trip for two adult passengers with child

<SIG_AirShopRQ CustomerID="TestUser"
<Itinerary>
<OriginDestination ODRef="1a" To="mow" From="par" Date="2013-03-10"/>
<OriginDestination ODRef="1b" To="par" From="mow" Date="2013-03-17"/>
</Itinerary>
<PaxTypes>
<PaxType Count="2" AgeCat="ADT" PTRef="adt0"/>
<PaxType Count="1" AgeCat="CHD" PTRef="child"/>
</PaxTypes>
</SIG_AirShopRQ>

Circle trip with direct flights only

Also used ignored AK list and promo code. The reply is limited by 10 options.

<SIG_AirShopRQ CustomerID="TestUser"
<Itinerary>
<OriginDestination ODRef="2a" To="mow" From="par" Date="2013-03-10"/>
<OriginDestination ODRef="2b" To="fra" From="mow" Date="2013-03-17"/>
<OriginDestination ODRef="2c" To="par" From="fra" Date="2013-03-21"/>
</Itinerary>
<PaxTypes>
<PaxType Count="1" AgeCat="ADT" PTRef="adt0"/>
</PaxTypes>
<FlightPref Cabin="B" IgnoredAirlines="BA AB" ConnPref="D"/>
<FarePref PromoCode="REDFISH"/>
<SearchOptions MaxResults="10"/>
</SIG_AirShopRQ>

Open jaw on LH and SU

<SIG_AirShopRQ CustomerID="TestUser"
<Itinerary>
<OriginDestination ODRef="3a" To="mow" From="par" Date="2013-03-10"/>
<OriginDestination ODRef="3b" To="fra" From="mow" Date="2013-03-17"/>
<OriginDestination ODRef="3c" To="lon" From="muc" Date="2013-03-21"/>
</Itinerary>
<PaxTypes>
<PaxType Count="1" AgeCat="ADT" PTRef="adt0"/>
</PaxTypes>
<FlightPref DesiredAirlines="LH SU"/>
<SearchOptions MaxResults="25"/>
</SIG_AirShopRQ>

Select an option from the shopping result

<SIG_AirShopRQ CustomerID="TestUser"
<SelectedShopOption SessionID="6546598453546313" OptionRef="24">
<SelectedFlights FlightRef="431"/>
<SelectedFlights FlightRef="433"/>
<SelectedFlights FlightRef="436"/>
</SelectedShopOption>
</SIG_AirShopRQ>

SIG_AirBookRQ

Create/retrieve/modify/ticket/cancel booking (PNR)
For detailed description see SIG Web Service data types definition and check latest WSDL at SIG Web Service Definition

Create PNR with one adult passenger

<SIG_AirBookRQ SessionID="" CustomerID="TestUser">
<SelectedShopOption SessionID="6546598453546313" OptionRef="24">
<SelectedFlights FlightRef="431"/>
<SelectedFlights FlightRef="433"/>
<SelectedFlights FlightRef="436"/>
</SelectedShopOption>
<Add>
<Passengers>
<Passenger AgeType="ADT" DOB="1967-08-13" PaxRef="1" Title="MR"
Surname="Smirnov" FFPAccount="111111111" FFPAirline="SU"
DocExpiration="2020-03-23" Name="Alexander" DocNumber="11111111111"/>
</Passengers>
<Contacts>
<Contact CtcData="+79991112233" CtcType="M" CtcRef="1"/>
</Contacts>
<Comments>
<Comment Text="Booked by TrTravel Co #111111(ag.#333)" CmtRef="1"/>
</Comments>
</Add>
</SIG_AirBookRQ>

Add remark into existing PNR

<SIG_AirBookRQ SessionID="6543842185465483485484" CustomerID="TestUser">
<BookingIdentity BookingReference="QS4HDG/1H" LeadPassenger="Ivanov"/>
<Add>
<Remarks>
<Remark RmkRef="1" PaxRefs="adt01" Text="peaches only" SSRCode="VGML" Quantity="1" FlightRef="zqEr453"/>
</Remarks>
</Add>
</SIG_AirBookRQ>

Modify passenger doc and contact data in existing PNR

<SIG_AirBookRQ SessionID="6543842185465483485484" CustomerID="TestUser">
<BookingIdentity BookingReference="QS4HDG/1H" LeadPassenger="Ivanov"/>
<Modify>
<Passengers>
<Passenger PaxRef="1" Title="MR" Surname="Smirnov" Name="Alexander" DocNumber="22222222222"/>
</Passengers>
<Contacts>
<Contact CtcData="+79991112345" CtcType="M" CtcRef="mob_1"/>
</Contacts>
</Modify>
</SIG_AirBookRQ>

Cancel entire itinerary

<SIG_AirBookRQ SessionID="6543842185465483485484" CustomerID="TestUser">
<BookingIdentity BookingReference="QS4HDG/1H" LeadPassenger="Ivanov"/>
<Cancel Itinerary="true">String</Cancel>
</SIG_AirBookRQ>

Cancel one segment only

<SIG_AirBookRQ SessionID="6543842185465483485484" CustomerID="TestUser">
<BookingIdentity BookingReference="QS4HDG/1H" LeadPassenger="Ivanov"/>
<Cancel>SVOCDG121226</Cancel>
</SIG_AirBookRQ>

Issue ticket with cash form of payment and display plain-text itinerary receipt

<SIG_AirBookRQ SessionID="6543842185465483485484" CustomerID="TestUser">
<BookingIdentity BookingReference="QS4HDG/1H" LeadPassenger="Ivanov"/>
<Issue>
<Payment Amount="10000.0" FOP="CASH"/>
<TicketMods>
<TicketMod>
<Endorsment>PP/111111111111</Endorsment>
<TourCode>WinterBeaches</TourCode>
<Comission>12%</Comission>
</TicketMod>
</TicketMods>
</Issue>
<Display ItineraryReceits="true"/>
</SIG_AirBookRQ>

Issue ticket with Credit Card form of payment and display plain-text itinerary receipt

<SIG_AirBookRQ SessionID="6543842185465483485484" CustomerID="TestUser">
<BookingIdentity BookingReference="QS4HDG/1H" LeadPassenger="Ivanov"/>
<Issue>
<Payment Amount="23006.0" FOP="CC">
<CreditCard AccountNumber="11xxxxxxxx44" ApprovalCode="AsdfASDf23rA" ExpirationDate="2014-12" CardHolder="Petrov Alexey" PaymentSystem="VI"/>
</Payment>
<TicketMods>
<TicketMod>
<Endorsment>PP/111111111111</Endorsment>
<TourCode>WinterBeaches</TourCode>
<Comission>12%</Comission>
</TicketMod>
</TicketMods>
</Issue>
<Display ItineraryReceits="true"/>
</SIG_AirBookRQ>

Display ticket data and itinerary receipt

<SIG_AirBookRQ SessionID="" CustomerID="TestUser">
<BookingIdentity BookingReference="QS4HDG/1H" LeadPassenger="Ivanov"/>
<Display TicketData="true" ItineraryReceits="true"/>
</SIG_AirBookRQ>

Retrieve PNR

<SIG_AirBookRQ SessionID="" CustomerID="TestUser">
<BookingIdentity BookingReference="QS4HDG/1H" LeadPassenger="Ivanov"/>
</SIG_AirBookRQ>

SIG_AirFareRuleRQ

Retrieve fare rules
For detailed description see SIG Web Service data types definition and check latest WSDL at SIG Web Service Definition

Request rules - all categories

<SIG_AirFareRuleRQ SessionID="6546598453546313" CustomerID="TestUser">
<Rules>
<RuleKey>00010101YNNNNNYNDME FRA 20130115OS KBUYRU 0008425NUC200084250000D9E40015F0F7YYNNNNNNNNNYNNNN EH 07000000000000000 OS N RU07004600064 </RuleKey>
<RuleKey>00010102YNNNNNYNFRA DME 20130129LH LNN10NW3 0010235NUC200102350000F1F00015C5E4YYNNNNNNNNNYNNNN EH 07000000000000000 LH N 10EU0040001 </RuleKey>
</Rules>
</SIG_AirFareRuleRQ>

@@ Line 89: / Line 89: @@
 Can be done at once - use subrequests '''BookingIdentity''', '''Issue''' and '''Display''' of request [[#SIG_AirBookRQ|SIG_AirBookRQ]] to issue tickets and display itinerary receipts.(''not implemented yet'')
-''Also possible to split the ticketing (as well as all other one-step tasks) on 2 or 3 steps (the same subrequest should be used) - in this case the '''SessionID''' returned by the 1st reply has to be used in subsequent requests.''
+Also possible to split the ticketing (as well as all other one-step tasks) on 2 or 3 steps (the same subrequest should be used) - in this case the '''SessionID''' returned by the 1st reply has to be used in subsequent requests.
 == Cancellation ==

SIG User Manual