...
Excerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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).
...