SIG API. Preface
From TAIS Documentation
(Difference between revisions)
| Line 1: | Line 1: | ||
| − | SIG - | + | SIG - a web service middleware 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 | ||
| + | # Flight+Fare Availability | ||
| + | # Fare Rule Display | ||
| + | # Booking and Pricing | ||
| + | # Ticket Issue | ||
| + | # Different forms of payment: CASH, CC, CASH+CC | ||
| + | # Booking Status & Repricing | ||
| + | # Booking Cancellation & Ticket Void | ||
| + | # Schedule Display | ||
| + | # Fare Display | ||
| − | + | Currently we manage interfaces with the following systems: | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
# Galileo | # Galileo | ||
# Sirena-Travel & Sirena-2.3 | # Sirena-Travel & Sirena-2.3 | ||
| Line 25: | Line 19: | ||
# Biletix Distribution System (Charter Database) | # Biletix Distribution System (Charter Database) | ||
| − | + | However every IBE/OTA can develop interface with every system in the list above independently they can benefit from SIG because | |
| − | # | + | # Fast new system integration. As fast as organization tasks solved |
| − | # | + | # All GDS/CRS technology concernes covered by SIG team. IBE/OTA developers do not need to know anything about GDS/CRS connected via SIG. Also they do not need to know Russian to deal with Russian systems |
| − | # | + | # No extra look/book invoices even in case of heavy loaded B2C sites. |
| − | # | + | # Comprehensive shopping engine able to find itineraries not offered by connected GDS/CRS shopping tools |
| + | # Smart price and availability caching tools | ||
| − | + | Currenlty SIG used by the following projects: [http://www.biletix.ru biletix.ru], [http://server.portbilet.ru portbilet.ru], [http://www.tutu.ru tutu.ru], [http://www.e-ticket.ru e-ticket.ru], [http://www.aviarost.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 basic functions at 01.10.2012. | |
Revision as of 19:22, 11 September 2012
SIG - a web service middleware 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
- Flight+Fare Availability
- Fare Rule Display
- Booking and Pricing
- Ticket Issue
- Different forms of payment: CASH, CC, CASH+CC
- Booking Status & Repricing
- Booking Cancellation & Ticket Void
- Schedule Display
- Fare Display
Currently we manage interfaces with the following systems:
- Galileo
- Sirena-Travel & Sirena-2.3
- SITA Gabriel
- Biletix Distribution System (Charter Database)
However every IBE/OTA can develop interface with every system in the list above independently they can benefit from SIG because
- Fast new system integration. As fast as organization tasks solved
- All GDS/CRS technology concernes covered by SIG team. IBE/OTA developers do not need to know anything about GDS/CRS connected via SIG. Also they do not need to know Russian to deal with Russian systems
- No extra look/book invoices even in case of heavy loaded B2C sites.
- Comprehensive shopping engine able to find itineraries not offered by connected GDS/CRS shopping tools
- Smart price and availability caching tools
Currenlty SIG 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 basic functions at 01.10.2012.
