Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Priority Boarding

Regardless of the assigned boarding group, passengers are now allowed to purchase a Priority Boarding service.

This Ancillary can be purchased by flight and passenger, it is not necessary, thus, to extend the Service to the whole booking.

When purchasing the Priority Boarding service, the assigned boarding group will be Group/Priority 2, which means boarding together with Plata and oneworld Ruby customers. For further information about normal Boarding priorities, please visit Iberia’s Priority Boarding Policy page.

Priority Boarding can be included in an OrderCreate (with or without payment), and held with the flights until the PaymentTimeLimit expires.

 

ServiceListRQ Message

When new services are released, we will publish the new applicable ServiceFilters, and you can include them as and when required, as per the following examples

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>

 

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.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
	<soap:Body>
		<ServiceListRS Version="5.000" PrimaryLangID="es" xmlns:ns2="http://www.iberia.com/IATA/NDC/SecurePayment/2017.2" xmlns="http://www.iata.org/IATA/EDIST/2017.2">
			<Document>
				<ReferenceVersion>5.000</ReferenceVersion>
			</Document>
			<Success/>
			<ShoppingResponseID>
				<ResponseID>Qm9va2luZ0AxNjgyNjAxMDg0MzA4LW5QUDl0</ResponseID>
			</ShoppingResponseID>
			<ALaCarteOffer OfferID="ALACARTE_IB71c41f00e411477796460aed645ae87d" Owner="IB">
				<OfferExpirationDateTime>2023-04-27T13:41:27.305Z</OfferExpirationDateTime>
				<ALaCarteOfferItem OfferItemID="ALACARTE_PRIORITY_IB71c41f00e411477796460aed645ae87d_01">
					<Eligibility>
						<PassengerRefs>ADULT_01</PassengerRefs>
						<SegmentRefs>IB043820230707</SegmentRefs>
					</Eligibility>
					<UnitPriceDetail>
						<TotalAmount>
							<SimpleCurrencyPrice Code="EUR">6.00</SimpleCurrencyPrice>
						</TotalAmount>
						<BaseAmount Code="EUR">6.00</BaseAmount>
						<Taxes>
							<Total Code="EUR">0.00</Total>
						</Taxes>
					</UnitPriceDetail>
					<Service ServiceID="PB_SERVICE_dd273ea5-26df-45f6-9018-c25c88365c0b">
						<ServiceDefinitionRef>PRIOBOARDINGSERVICE</ServiceDefinitionRef>
					</Service>
				</ALaCarteOfferItem>
			</ALaCarteOffer>

 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.

<ServiceDefinitionList>
	<ServiceDefinition ServiceDefinitionID="PRIOBOARDINGSERVICE">
		<Name>PRIORITY BOARDING</Name>
		<Encoding>
			<RFIC>E</RFIC>
			<SubCode>0G6</SubCode>
		</Encoding>
		<Descriptions>
			<Description>
				<Text>PRIORITY BOARDING</Text>
			</Description>
		</Descriptions>
		<BookingInstructions>
			<SSRCode>BDPR</SSRCode>
			<Method>SSR</Method>
		</BookingInstructions>
		<Detail>
			<ServiceItemQuantityRules>
				<MaximumQuantity>1</MaximumQuantity>
			</ServiceItemQuantityRules>
		</Detail>
	</ServiceDefinition>
</ServiceDefinitionList>

 

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

<Query>
	<Order>
		<Offer OfferID="IBc19320d37eab41f38e6088c64a5b3a9eOC" Owner="IB" ResponseID="Qm9va2luZ0AxNjgyNjAxMDg0MzA4LW5QUDl0">
			<OfferItem OfferItemID="IBc19320d37eab41f38e6088c64a5b3a9eOC_01">
				<PassengerRefs>ADULT_01</PassengerRefs>
			</OfferItem>
		</Offer>
		<Offer OfferID="ALACARTE_IB71c41f00e411477796460aed645ae87d" Owner="IB" ResponseID="Qm9va2luZ0AxNjgyNjAxMDg0MzA4LW5QUDl0">
			<OfferItem OfferItemID="ALACARTE_PRIORITY_IB71c41f00e411477796460aed645ae87d_01">
				<PassengerRefs>ADULT_01</PassengerRefs>
			</OfferItem>
		</Offer>
	</Order>

 

OderViewRS Message

In the OrderViewRS, the Priority Boarding Ancillary is shown in the following way.

First, the OrderItem:

<OrderItem OrderItemID="IBc19320d37eab41f38e6088c64a5b3a9eOC_02">
	<PriceDetail>
		<TotalAmount>
			<SimpleCurrencyPrice Code="EUR">6.00</SimpleCurrencyPrice>
		</TotalAmount>
		<BaseAmount Code="EUR">6.00</BaseAmount>
		<Taxes>
			<Total Code="EUR">0.00</Total>
		</Taxes>
	</PriceDetail>
	<Service ServiceID="PRIORITY_BOARDING_IB043820230707_01" ServiceStatus="HK">
		<PassengerRef>ADULT_01</PassengerRef>
		<ServiceDefinitionRef SegmentRef="IB043820230707">PRIOBOARDINGSERVICE</ServiceDefinitionRef>
	</Service>
</OrderItem>

And the ServiceDefinition:

<ServiceDefinitionList>
	<ServiceDefinition ServiceDefinitionID="PRIOBOARDINGSERVICE">
		<Name>PRIORITY BOARDING</Name>
		<Encoding>
			<RFIC>E</RFIC>
			<SubCode>0G6</SubCode>
		</Encoding>
		<Descriptions>
			<Description>
				<Text>PRIORITY BOARDING</Text>
			</Description>
		</Descriptions>
		<BookingInstructions>
			<SSRCode>BDPR</SSRCode>
			<Method>SSR</Method>
		</BookingInstructions>
		<Detail>
			<ServiceItemQuantityRules>
				<MaximumQuantity>1</MaximumQuantity>
			</ServiceItemQuantityRules>
		</Detail>
	</ServiceDefinition>
</ServiceDefinitionList>

 

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:

<MediaList>
	<Media ListKey="Legal-Information">
		<MediaLink>http://www.iberia.com/es/informacion-legal/</MediaLink>
	</Media>
	<Media ListKey="Cabin-features">
		<MediaLink>https://www.iberia.com/es/un-nuevo-concepto-de-volar/</MediaLink>
	</Media>
	<Media ListKey="Media-Checked-Baggage">
		<MediaLink>https://www.iberia.com/es/equipajes/franquicia-bodega/</MediaLink>
	</Media>
</MediaList>

  • No labels