Priority Boarding
Â
Priority Boarding |
---|
Our Priority Boarding service can be purchased through our NDC channel. This Ancillary can be purchased for individual flights and passengers, and not necessarily for the whole booking.
When purchasing the Priority Boarding service, the assigned boarding group will be Group/Priority 2, which means boarding together with Iberia Plus Plata and oneworld Ruby customers. For further information about normal Boarding priorities, please visit Iberia’s Priority Boarding Policy page.
Priority Boarding can ONLY be included in an OrderCreate (with payment), or purchased and added to an already paid Order. Please note that the absence of a payment time limit for an OfferItem signifies that the item must be paid for at time of booking.
Â
ServiceListRQ Message |
---|
The following examples, here for illustrative purposes.
Please, note that both GroupCode
and SubGroupCode
information are being taken from this table, and that the above-mentioned example combines two ancillaries (Bags together with Priority Boarding).
<Parameters>
<ServiceFilters>
<ServiceFilter>
<GroupCode>TS</GroupCode>
<SubGroupCode>PR</SubGroupCode>
</ServiceFilter>
<ServiceFilter>
<GroupCode>BG</GroupCode>
</ServiceFilter>
</ServiceFilters>
</Parameters>Â
An example of a ServiceListRQ in the prime shopping flow, following the OfferPrice could look something like the following:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header/>
<soapenv:Body>
<ServiceListRQ Version="5.000" PrimaryLangID="es" xmlns="http://www.iata.org/IATA/EDIST/2017.2">
<PointOfSale>
<Location>
<CountryCode>ES</CountryCode>
</Location>
</PointOfSale>
<Document>
<ReferenceVersion>1.0</ReferenceVersion>
</Document>
<Party>
<Sender>
<TravelAgencySender>
<IATA_Number>########</IATA_Number>
<AgencyID>firstAgency</AgencyID>
</TravelAgencySender>
</Sender>
<Participants>
<Participant>
<AggregatorParticipant SequenceNumber="1">
<AggregatorID>00000022</AggregatorID>
</AggregatorParticipant>
</Participant>
</Participants>
</Party>
<Parameters>
<ServiceFilters>
<ServiceFilter>
<GroupCode>TS</GroupCode>
<SubGroupCode>PR</SubGroupCode>
</ServiceFilter>
</ServiceFilters>
</Parameters>
<ShoppingResponseID>
<ResponseID>Qm9va2luZ0AxNjgyNjAxMDg0MzA4LW5QUDl0</ResponseID>
</ShoppingResponseID>
<Query>
<Offers>
<Offer>
<OfferID Owner="IB">IBc19320d37eab41f38e6088c64a5b3a9eOC</OfferID>
<OfferItemIDs>
<OfferItemID Owner="IB">IBc19320d37eab41f38e6088c64a5b3a9eOC_01 </OfferItemID>
</OfferItemIDs>
</Offer>
</Offers>
</Query>
</ServiceListRQ>
</soapenv:Body>
</soapenv:Envelope>
The above example is in the presale flow. For a postsale flow, simply replace the OfferID within the Query section with the OrderID:
<Query>
<OrderID Owner="IB">IB24847487859643f69318ea7fa100e3beOC</OrderID>
</Query>
ServiceListRS Message |
---|
All services offered are included within the ServiceList message response. This will evolve as more services are offered through the NDC channel.
OfferItem - in ServiceListRS
The OfferItem shows the unit price of the Service for the applicable passengers and flight segments.
 The ServiceDefinitionList contains a list of the different Services each defined as necessary.
When there is more than one service, then the number of <ServiceDefinitionRef>
elements gives you the number of those services. We do not recommend you use the numbers in the Name or the Description Text to discern the number of services.
The ServiceDefinitionRef
references the ServiceID
, which describes the requested service. The SubCode
specifically relates to this product (0G6
).
Using the RFIC together with the Subcode together with the ATPCo Optional Services Industry Sub Codes., the Grouping and SubGrouping of the services can be achieved.
Â
OderCreateRQ Message |
---|
From the OrderCreate Request, the following piece of code shows that Priority Boarding is assigned to the passenger.
Since these samples are being extracted from the same Flow, we can see that the OfferID is the same reported in the ServiceListRQ (<OfferID Owner="IB">IBc19320d37eab41f38e6088c64a5b3a9eOC</OfferID>
), and so is the OfferItemID (<OfferItemID Owner="IB">IBc19320d37eab41f38e6088c64a5b3a9eOC_01 </OfferItemID>
).
If you are adding the ancillary to an already existing, and paid for, Order then the OrderChangeRQ is used as per the following:
OderChangeRQ Message |
---|
When adding ancillaries to an existing Order, you reference the existing OrderID and the OfferItem’s that you wish to purchase from the previous ServiceListRQ.
Remember:
Ancillaries cannot be added to an unpaid Order.
Payment for the ancillaries must be included, as you cannot add an unpaid ancillary to a paid Order.
OderViewRS Message |
---|
In the OrderViewRS, the Priority Boarding Ancillary is shown in the following way.
First, the OrderItem:
And the ServiceDefinition:
Â
MediaList |
---|
Here is where we put URLs that can be used to link to additional information such as rich media and other useful information for the customer:
Â
Examples of messages with complete flows can be downloaded from here.
Â
Â