...
Excerpt | |||||
---|---|---|---|---|---|
|
...
What types of passengers are used in the API?
3 types of passengers are used:
- adult (ADT) — passengers from 12 years and older
- child (CHD) — passengers from 2 to 12 years
- infant (INF) — passengers under 2 years
Note | ||
---|---|---|
| ||
If the passenger is 2 years old, he is a CHD If the passenger is 12 years old, he is an ADT |
...
What types of payment can be used?
Only one payment method is used - invoice
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<Type>
<Code>MS</Code>
</Type>
<Other>
<Remarks>
<Remark>IN*A*AGENT_NAME</Remark>
</Remarks>
</Other> |
where:
|
MS — payment type code (invoice)
IN*A*AGENT_NAME — agent details
Note | ||
---|---|---|
| ||
Processing of payments isn't on our side. |
...
How can I get information about flights commissions and manage agency fees?
...
You need to contact the sales department.
...
|
# | Enviroment | Endpoint |
---|---|---|
1 | TEST | https://qa-gaia.s7.ru/agent-api/gaia |
2 | PROD | https://api.s7.ru/agent-api/gaia |
|
...
Is the Multi-City method implemented in API?
...
Yes.
You can read about it here ( Oops! It will be a link to the documentation here as soon as possible!)
...
|
...
|
...
|
...
|
You can read about it here Scenarios
|
...
|
...
|
...
|
...
|
...
Can I get a terminal text vuew of the current PNR data? Or just build a template from an XML response?
...
No, currently only XML display is available.
...
Can I add DOCO DOCA information?
...
No, currently only DOCS, FOID and FQTV SSRs are available.
...
How to access the test environment?
...
|
...
|
...
...
|
...
Is the refund method implemented in API?
...
|
...
|
...
|
...
...
|
|
...
|
...
|
...
We get an error:
"032 - SI"
...
Search operation questions
...
What does the PenaltyList block mean (AirShoppingRS)?
...
Fare penalties informarion block.
Penalties types:
NO-SHOW (NS) — a situation, when the passenger fails to show for the flight before the check-in closing and notify the carrier of cancelling the carriage.
PRIOR DEPARTURE (PDE) — penalties if the passenger want before departure to change the conditions of transportation on the previously purchased air ticket.
AFTER DEPARTURE (ADE) — penalties if the passenger want after departure to change the conditions of transportation on the previously purchased air ticket.
You can see the full fare rules application by FareRulesRQ
...
- Low Fare search — search for offers with a minimal price. Solutions include information for a whole requested journey (no matter OW or RT).
- Branded fares search — solutions include information only for requested slice of journey (only inbound or outbound itinerary). Pricing also divided by fare family and mostly includes 4 or 2 sub solutions (Basic Economy, Flex Economy, Basic Business, Flex Business) for each itinerary solution.
...
You can add all types of passengers and specify there quantity (from 0 to 9)
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<ns3:Travelers>
<ns3:Traveler>
<ns3:AnonymousTraveler>
<ns3:PTC Quantity="1">ADT</ns3:PTC>
</ns3:AnonymousTraveler>
</ns3:Traveler>
<ns3:Traveler>
<ns3:AnonymousTraveler>
<ns3:PTC Quantity="0">CHD</ns3:PTC>
</ns3:AnonymousTraveler>
</ns3:Traveler>
<ns3:Traveler>
<ns3:AnonymousTraveler>
<ns3:PTC Quantity="0">INF</ns3:PTC>
</ns3:AnonymousTraveler>
</ns3:Traveler>
</ns3:Travelers> |
You can specify only the required types
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<ns3:Travelers>
<ns3:Traveler>
<ns3:AnonymousTraveler>
<ns3:PTC Quantity="1">ADT</ns3:PTC>
</ns3:AnonymousTraveler>
</ns3:Traveler>
</ns3:Travelers> |
...
Yes.
You can read about it here ( Oops! It will be a link to the documentation here as soon as possible!)
...
Yes.
You can read about it here Scenarios
...
Yes. It's necessary to specify the following search parameter:
Envelope /Body /AirShoppingRQ /Preferences /Preference /FlightPreferences /Characteristic /DirectPreferences="Preferred"
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Preferences>
<Preference>
<FlightPreferences>
<Characteristic>
<DirectPreferences>Preferred</DirectPreferences>
</Characteristic>
</FlightPreferences>
</Preference>
</Preferences> |
...
You can see this parameter in the ItinReshopRS.
You can see an example here OW + 2xADT 2xCHD 2xINF + Transfer + SPA | v0.35 | reprice operation
...
Yes, but you can see information about trasits only in AirShoppingRS. In other RQ/RS trasits information isn't displayed.
You can see an example here OW + 1xADT + Transit + S7 | v0.35 | searchFlight operation
...
Book operation questions
...
What types of documents are used?
PP tyep only, but in the ID field you can enter information about any document:
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<ns3:PassengerDocument>
<ns3:Type>PP</ns3:Type>
<ns3:ID>131231231222</ns3:ID>
<ns3:BirthCountry>RU</ns3:BirthCountry>
<ns3:DateOfIssue>2008-06-06</ns3:DateOfIssue>
<ns3:DateOfExpiration>2028-06-06</ns3:DateOfExpiration>
<ns3:CountryOfResidence>RU</ns3:CountryOfResidence>
</ns3:PassengerDocument> |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<ns3:PassengerDocument>
<ns3:Type>PP</ns3:Type>
<ns3:ID>rbrtrtvgb123456</ns3:ID>
<ns3:BirthCountry>RU</ns3:BirthCountry>
<ns3:DateOfIssue>2008-06-06</ns3:DateOfIssue>
<ns3:DateOfExpiration>2028-06-06</ns3:DateOfExpiration>
<ns3:CountryOfResidence>RU</ns3:CountryOfResidence>
</ns3:PassengerDocument> |
...
Yes, but you need to consider the following logic:
e-mails — for each e-mail created a separate Contact element
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<ns3:Contacts>
<ns3:Contact>
<ns3:EmailContact>
<ns3:Address>l.conelly@mail.ru</ns3:Address>
</ns3:EmailContact>
</ns3:Contact>
<ns3:Contact>
<ns3:EmailContact>
<ns3:Address>l.ercrvev@mail.ru</ns3:Address>
</ns3:EmailContact>
</ns3:Contact>
</ns3:Contacts> |
phoneContact — you can specify several phone numbers in one PhoneContact block
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<ns3:Contacts>
<ns3:Contact>
<ns3:PhoneContact>
<ns3:Number CountryCode="+375" AreaCode="29">3277438</ns3:Number>
<ns3:Number CountryCode="+375" AreaCode="29">44444444</ns3:Number>
<ns3:Number CountryCode="+375" AreaCode="29">66666666</ns3:Number>
<ns3:Number CountryCode="+375" AreaCode="29">77777777</ns3:Number>
</ns3:PhoneContact>
</ns3:Contact>
</ns3:Contacts> |
both types
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<ns3:Contacts>
<ns3:Contact>
<ns3:PhoneContact>
<ns3:Number CountryCode="+375" AreaCode="29">3277438</ns3:Number>
<ns3:Number CountryCode="+375" AreaCode="29">44444444</ns3:Number>
<ns3:Number CountryCode="+375" AreaCode="29">66666666</ns3:Number>
<ns3:Number CountryCode="+375" AreaCode="29">77777777</ns3:Number>
</ns3:PhoneContact>
<ns3:EmailContact>
<ns3:Address>l.conelly@mail.ru</ns3:Address>
</ns3:EmailContact>
</ns3:Contact>
<ns3:Contact>
<ns3:EmailContact>
<ns3:Address>l.ercrvev@mail.ru</ns3:Address>
</ns3:EmailContact>
</ns3:Contact>
</ns3:Contacts> |
...
You can't use the following characters:
; : * ' " ^ { } [ ] < > & # ! ` = %
...
Required passenger data:
- Surname
- Given
- Age
- Contacts
- PassengerDocument
...
In OrderCreateRQ you need to fill the PassengerDocument block.
In GDS both SSRs are created.
...
The next filling of the PassengerDocument block is required:
ADT, CHD, INF
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<ns3:PassengerDocument>
<ns3:Type>PP</ns3:Type>
<ns3:ID>131231231222</ns3:ID>
<ns3:BirthCountry>RU</ns3:BirthCountry>
<ns3:DateOfIssue>2008-06-06</ns3:DateOfIssue>
<ns3:DateOfExpiration>2028-06-06</ns3:DateOfExpiration>
<ns3:CountryOfResidence>RU</ns3:CountryOfResidence>
</ns3:PassengerDocument> |
CHD, INF
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<ns3:PassengerDocument>
<ns3:Type>PP</ns3:Type>
<ns3:ID>rbrtrtvgb123456</ns3:ID>
<ns3:BirthCountry>RU</ns3:BirthCountry>
<ns3:DateOfIssue>2008-06-06</ns3:DateOfIssue>
<ns3:DateOfExpiration>2028-06-06</ns3:DateOfExpiration>
<ns3:CountryOfResidence>RU</ns3:CountryOfResidence>
</ns3:PassengerDocument> |
...
BirthCountry — сountry of issue
CountryOfResidence — citizenship
...
DOCS
FOID
CHLD
INFT
FQTV
TKNE
XBAG
EXST
...
ChangeBook operation questions
...
Yes.
You can read about it here ( Oops! It will be a link to the documentation here as soon as possible!)
...
Yes.
You can read about seats here ( Oops! It will be a link to the documentation here as soon as possible!)
You can read about bags here ( Oops! It will be a link to the documentation here as soon as possible!)
...
Yes.
You can read about it here ( Oops! It will be a link to the documentation here as soon as possible!)
...
When the OrderChangeRQ is executed, we get an error:
<ns3:Error Type="LOC" Tag="Property change_book_request can not be empty" RecordID="CHNG_BOOK_RQ_IS_EMPTY"/>.
...
DemandTickets operation questions
...
ETK - Electronic Ticket. Document confirming the payment of the itinerary.
EMD - Electronic Miscellaneous Document. Document confirming the payment of services
Note | ||
---|---|---|
| ||
ETK Type code - 702 EMD Type code - Y |
...
Issue of terminal type of ETK/EMD is not implemented. You can read the issued ETK/EMD using the operation AirDocDisplayRQ.
You can read about it here ( Oops! It will be a link to the documentation here as soon as possible!)
Note | ||
---|---|---|
| ||
ETK Type code - 702 EMD Type code - Y |
...
Yes, this is a mandatory parameter. Corresponds to RMK type in Gabriel - text field.
It's forbidden to use the following symbols: ; : * ' " ^ { } [ ] < > & # ! ` = %
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<Payment>
<Type>
<Code>MS</Code>
</Type>
<Other>
<Remarks>
<Remark>IN*QUW1725</Remark>
</Remarks>
</Other>
</Payment> |
|
VoidTicket operation questions
...
- You can void the ticket until 23:59 of the current day (day of ticket issue).
Time in 0 time zone (0UTC).
- Voided the ticket can only use the same validator, under which the ticket was issued. Make sure you use the same validator.
- In the requests you need to use the following codes:
ETK Type code - 702
EMD Type code - Y
...
You can void the ticket until 23:59 of the current day (day of ticket issue).
Time in 0 time zone (0UTC).
...