Excerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
|
...
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
# | Question | Answer | |||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | What types of documents are used? | PP tyep only, but in the ID field you can enter information about any document:
| |||||||||||||||||||||||||||||||||
2 | Can I specify multiple phone numbers and emails? | Yes, but you need to consider the following logic:
| |||||||||||||||||||||||||||||||||
3 | How to specify TTL? | The TTL is calculated automatically. It's possible to enter it manually, but we recommend not using this functionality, as it will be closed soon. | |||||||||||||||||||||||||||||||||
4 | What characters are forbidden for input? | You can't use the following characters: ; : * ' " ^ { } [ ] < > & # ! ` = % | |||||||||||||||||||||||||||||||||
5 | What passenger data are required? | Required passenger data:
| |||||||||||||||||||||||||||||||||
6 | Is it possible to change the automatic TTL? | There is no such possibility, the TTL is calculated according to the airline requirements. | |||||||||||||||||||||||||||||||||
7 | Is the automatic time limit matches for the airline fare rules? | Yes. TTL is calculated according to the airline requirements, considering the partner airlines. | |||||||||||||||||||||||||||||||||
8 | In what format are passport data entered (DOCS/FOID)? | In OrderCreateRQ you need to fill the PassengerDocument block. In GDS both SSRs are created. | |||||||||||||||||||||||||||||||||
9 | Why is it necessary to enter the date of passport issuance? | The next filling of the PassengerDocument block is required: ADT, CHD, INF
CHD, INF
| |||||||||||||||||||||||||||||||||
10 | Why there is no link between an infant and an adult? | The link exists, but is used only at the stage of issuing the ticket for infant. | |||||||||||||||||||||||||||||||||
11 | What do the elements BirthCountry/CountryOfResidence describe? | BirthCountry — сountry of issue CountryOfResidence — citizenship | |||||||||||||||||||||||||||||||||
12 | Will EMD information be displayed in PNR if EMD is issued? | Yes, it will be displayed like ticket information | |||||||||||||||||||||||||||||||||
13 | What SSR codes are implemented? | DOCS FOID CHLD INFT FQTV TKNE XBAG EXST | |||||||||||||||||||||||||||||||||
14 | Why there is no possibility to enter DOCA and DOCO SSRs? | At the stages of booking and ticketing, we don't require visa data. Visa is required on check-in. | |||||||||||||||||||||||||||||||||
15 | Does theTTL guarantee automatic cancellation of the reservation? | Yes. Booked seats will be free. |
...