Bags
Â
Bags |
---|
Through NDC, you can purchase additional bags of 15kg, 23kg, and 32kg.
For information on Iberia’s Checked Baggage Policy, please see Baggage in the hold - Iberia Spain
Bags (15kg, 23 kg and 32 kg) may be included in an OrderCreate (with or without payment), and held (on hold) with the flights until the Payment Time Limit (applicable to the bags) expires, which may be more restrictive than the Payment Time Limit for the flights. 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.
Maintaining backward compatibility, bags can be purchased in both Pre-Sale and Servicing flows, for this no ServiceFilter/GroupCode needs to be sent in the ServiceListRQ message
To purchase bags of 15kg, 23kg or 32kg, the ServiceFilter/GroupCode needs to be sent in the ServiceListRQ message as per the following example (please, refer to the SubGroup and Group codes displayed in this table):
<Parameters>
<ServiceFilters>
<ServiceFilter>
<GroupCode>BG</GroupCode>
</ServiceFilter>
</ServiceFilters>
</Parameters>
The information regarding the price and details is included in the message response, later displayed in these examples.
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:
<Parameters>
<ServiceFilters>
<ServiceFilter>
<GroupCode>BG</GroupCode>
</ServiceFilter>
<ServiceFilter>
<GroupCode>TS</GroupCode>
<SubGroupCode>PR</SubGroupCode>
</ServiceFilter>
</Parameters>
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).
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>11112220</IATA_Number>
<AgencyID>firstAgency</AgencyID>
</TravelAgencySender>
</Sender>
<Participants>
<Participant>
<AggregatorParticipant SequenceNumber="1">
<AggregatorID>00000022</AggregatorID>
</AggregatorParticipant>
</Participant>
</Participants>
</Party>
<Parameters>
<ServiceFilters>
<ServiceFilter>
<GroupCode>BG</GroupCode>
</ServiceFilter>
</ServiceFilters>
</Parameters>
<ShoppingResponseID>
<ResponseID>Qm9va2luZ0BHVy0xNjgxNzI2NzkwMDI5LUU4TXVo</ResponseID>
</ShoppingResponseID>
<Query>
<Offers>
<Offer>
<OfferID Owner="IB">IB1f565db470e14d5ebb4038fa101152c0OC</OfferID>
<OfferItemIDs>
<OfferItemID Owner="IB">IB1f565db470e14d5ebb4038fa101152c0OC_01 </OfferItemID>
</OfferItemIDs>
</Offer>
</Offers>
</Query>
</ServiceListRQ>
</soapenv:Body>
</soapenv:Envelope>
ServiceListRS Message |
---|
All services offered are included within the ServiceList message response, also on hold. This will evolve as more services are offered through the NDC channel.
If the ServiceFilter is omite, then only the 23Kgs bags will be returned, maintaining backward compatibility with our initial implementation. However, with the new services being added, it is necessary to include the ServiceFilter if you want to sell them.
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.
In the case of a single service there is no ServiceBundle section, so the number of services is deducible as 1. When there are 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.
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.
As the purchase of multiple bags is solved here using the ServiceBundle, made up of various individual bag services, the NotPermitted
combinations are shown to prevent the purchase of a number of bags that would exceed the maximum quantity allowed. To purchase multiple bags at the same weight, you must select the ALaCarteOfferItem
for the amount of bags you want, and not select multiple ALaCarteOfferItem
.
OrderCreateRQ Message |
---|
Service Bundle
From the OrderCreate Request (and as an example of the various combinations) the following code shows that bags with different weights are being assigned to different passengers.
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">IB1f565db470e14d5ebb4038fa101152c0OC</OfferID>
), and so is the OfferItemID (<OfferItemID Owner="IB">IB1f565db470e14d5ebb4038fa101152c0OC_01 </OfferItemID>
).
Â
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.
Â
OrderViewRS Message |
---|
In the OrderViewRS the Bag 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.
Â
Â