SIG API. Preface
From TAIS Documentation
(Difference between revisions)
m |
|||
| (11 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | SIG | + | 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 |
| − | # | + | <br /> |
| − | # | + | Currently SIG manages interfaces with the following systems: |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
# Galileo | # Galileo | ||
# Sirena-Travel & Sirena-2.3 | # Sirena-Travel & Sirena-2.3 | ||
# SITA Gabriel | # SITA Gabriel | ||
# Biletix Distribution System (Charter Database) | # Biletix Distribution System (Charter Database) | ||
| + | <br /> | ||
| + | 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: [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. <br /> | |
| − | + | <br /> | |
| − | + | 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. | |
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 21:43, 11 September 2012
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.
