...
Table of Contents | ||||
---|---|---|---|---|
|
Special Service Request (SSR) |
---|
SSR’s is a legacy concept used to request special services for passengers on flights. Initially this service was created for, and is still used for, the requesting of free services, such as Wheelchairs, Special Dietary Meals, services for Passengers with Reduced Mobility, etc
Some SSR are inventory controlled due to operational reasons, and therefore can be rejected due to capacity restraints.
Some services are not accepted by our code-share partners, and therefore may be rejected.
The following are the SSRs that can be requested through our NDC channel.These services must be requested in the OfferPrice service and subsequently booked in OrderCreate. They cannot be added to a previously created Order in a servicing flow.
SSR Code Table |
---|
SSR Code | Purpose |
---|---|
BLND | Blind Passenger |
DEAF | Deaf Passenger |
DPNA | Disabled Passenger, with intellectual or developmental disability needing assistance (specify details) |
WCHR | Wheelchair for passengers who can ascend/descend steps, and are able to make own way to/from cabin seat, but require wheelchair for distances. |
WCHS | Passenger cannot ascend/descend steps, but is able to make own way to/from cabin seat; requires wheelchair for distances and must be carried up/down steps. |
The code “DISA” “DISA” can be included in the request, and this will return all the Special Services for disabilities that we offer in the response.
ServiceListRQ Message |
---|
The applicable SSR Codes, that you can include as and when required, are taken from the table above.
To request an SSR it should be included in the OfferPriceRQ ServiceListRQ message as a Qualifier
:
Code Block | ||
---|---|---|
| ||
<Qualifier> <SpecialNeedQualifiers> <Code>BLND</Code> </SpecialNeedQualifiers> </Qualifier> |
The code “DISA” can be included in the request, and this will return all the Special Services for disabilities that we offer in the response.
...
OfferPriceRS Message
...
Note: Formerly, the only way to request SSRs was through OfferPriceRQ message, which is still possible to maintain backward compatibility. However, we recommend that from now on the ServiceList is used.
It should be noted that if SSRs are requested in both the OfferPriceRQ and the ServiceListRQ, then an error will be returned (please, see an example of this scenario in our Special Services Error Messages page).
ServiceListRS Message |
---|
ALaCarteOfferItem
The Special Services are returned in the ServiceListRS as ALaCarteOfferItems, for the passengers and flight segments for which they can be requested. This does not mean that the service is necessarily available, and is subject to confirmation at time of booking.
Code Block | ||
---|---|---|
| ||
<OtherOffers> <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>Qm9va2luZ0BHVy0xNjk1NjUyMTg3MjcwLTRSWERW</ResponseID> </ShoppingResponseID> <ALaCarteOffer OfferID="ALACARTE_SSR_IBef14deece1b743bab80c8bff759339c3IB48ed39bdf2204eb19f485e1357abe0a3" Owner="IB"> <OfferExpirationDateTime>2023-0209-20T1525T14:3459:0149.654Z<506Z</OfferExpirationDateTime> <ALaCarteOfferItem OfferItemID="IBb5fce81aa5b548f79086259d216c3181OCALACARTE_SSR_IB48ed39bdf2204eb19f485e1357abe0a3_BLND"> <Eligibility> <PassengerRefs>ADULT_01 ADULT_02 ADULT_03 ADULT_04<02</PassengerRefs> <SegmentRefs>IB343620230911<<SegmentRefs>IB042620240108 IB042520240128</SegmentRefs> </Eligibility> <UnitPriceDetail> <TotalAmount> <SimpleCurrencyPrice Code="EUR">0.00</SimpleCurrencyPrice> </TotalAmount> <BaseAmount Code="EUR">0.00</BaseAmount> <Taxes> <Total Code="EUR">0.00</Total> </Taxes> </UnitPriceDetail> <Service ServiceID="SSR_SNBLND_c266f83bd0730723-195cab16-4af4405a-a5f98c44-7f28fb18d1116adbd32a0efc"> <ServiceDefinitionRef>SPECIAL_NEED-BLND</ServiceDefinitionRef> </Service> </ALaCarteOfferItem> </ALaCarteOffer> </OtherOffers> |
...
ServiceDefinitionList
ContainsServiceDefinition
with additional information describing each of the specific ALaCarteOfferItem
, to which they are linked using the ServiceDefinitionRef
in the ALaCarteOfferItem
.
The BookingInstructions
are used by certain system providers for legacy reasons.
MaximumQuantity
is the amount services permitted for each passenger per flight.
Code Block | ||
---|---|---|
| ||
<ServiceDefinitionList> <ServiceDefinition ServiceDefinitionID="SPECIAL_NEED-BLND"> <Name>Pasajero<Name>Blind ciego<Passenger</Name> <Descriptions> <Description> <Text>Solicite<Text>Request servicioService deAnimal animalesif sitravelling viajawith con uno<one</Text> </Description> </Descriptions> <BookingInstructions> <SSRCode>BLND</SSRCode> <<Method>SSR</BookingInstructions>Method> </ServiceDefinition> <...> </ServiceDefinitionList> </DataLists> |
...
OrderCreate Message
...
BookingInstructions>
<Detail>
<ServiceItemQuantityRules>
<MaximumQuantity>1</MaximumQuantity>
</ServiceItemQuantityRules>
</Detail>
</ServiceDefinition>
</ServiceDefinitionList> |
OrderCreateRQ Message |
---|
The OfferID
for each is ALaCarteOfferItem
is included in an Offer in the
OrderCreateRQ to book the service.
Code Block | ||
---|---|---|
| ||
<Query> <Order> <...> <Order> <Offer OfferID="IB01db6efac4044bd7b6d65113a60b5281OC" Owner="IB" ResponseID="Qm9va2luZ0BHVy0xNjk1NjUyMTg3MjcwLTRSWERW"> <OfferItem OfferItemID="IB01db6efac4044bd7b6d65113a60b5281OC_01"> <PassengerRefs>ADULT_01 ADULT_02</PassengerRefs> </OfferItem> <OfferItem OfferItemID="IB01db6efac4044bd7b6d65113a60b5281OC_02"> <PassengerRefs>INFANT_01</PassengerRefs> </OfferItem> </Offer> <Offer OfferID="ALACARTE_SSR_IBef14deece1b743bab80c8bff759339c3IB48ed39bdf2204eb19f485e1357abe0a3" Owner="IB" ResponseID="Qm9va2luZ0BHVy0xNjc2OTA1NDM5MjM3LWFpOUMzQm9va2luZ0BHVy0xNjk1NjUyMTg3MjcwLTRSWERW"> <OfferItem OfferItemID="IBb5fce81aa5b548f79086259d216c3181OCALACARTE_SSR_IB48ed39bdf2204eb19f485e1357abe0a3_BLND"> <PassengerRefs>ADULT_01 ADULT_01<02</PassengerRefs> <ServiceSelection ServiceID="SSR_SNBLND_c266f83bd0730723-195cab16-4af4405a-a5f98c44-7f28fb18d1116adbd32a0efc"> <ServiceDefinitionID>SPECIAL_NEED-BLND</ServiceDefinitionID> </ServiceSelection> </OfferItem> </Offer> |
together with the ServiceDefinition in the same way as it is returned in the OfferPriceRS.
</Order> |
The ServiceDefinition
is only required in the OrderCreateRQ if and when additional information needs to be included, in the Description
/ Text
, with the Special Service Request.
The correct SSRCode
must be included otherwise the NDC_DIST_2164 error will be returned.
The following is an example of the type of additional information that can be communicated to us:
Code Block | ||
---|---|---|
| ||
<DataLists> <...> <ServiceDefinitionList> <ServiceDefinition ServiceDefinitionID="SPECIAL_NEED-BLND"> <Name>Pasajero ciego< <Name>Blind Passenger</Name> <Descriptions> <Descriptions> <Description refs="ADULT_01 ADULT_02"> <Text>Please supply security instructions <Text>Solicite servicio de animales si viaja con uno</Text> in braile</Text> </Description> </Descriptions> <BookingInstructions> <BookingInstructions> <SSRCode>BLND</SSRCode> </BookingInstructions> </ServiceDefinition> </ServiceDefinitionList> </DataLists> |
OrderViewRS Message |
---|
The service will then be returned in the OrderViewRS as an OrderItem with with zero price for those services that are offered free of charge .and without any EMD:
Code Block | ||
---|---|---|
| ||
<OrderItems> <OrderItem OrderItemID="IBb5fce81aa5b548f79086259d216c3181OCIB01db6efac4044bd7b6d65113a60b5281OC_1104"> <PriceDetail> <TotalAmount> <SimpleCurrencyPrice Code="EUR">0.00</SimpleCurrencyPrice> </TotalAmount> <BaseAmount Code="EUR">0.00</BaseAmount> <Taxes> <Total Code="EUR">0.00</Total> </Taxes> </PriceDetail> <Service ServiceID="SPECIAL_NEED_IB343620230911IB042520240128_0102" ServiceStatus="HK"> <PassengerRef>ADULT_01</PassengerRef> <ServiceDefinitionRef SegmentRef="IB343620230911IB042520240128">SPECIAL_NEED-BLND</ServiceDefinitionRef> </Service> <Service ServiceID="SPECIAL_NEED_IB042620240108_01" ServiceStatus="HK"> <PassengerRef>ADULT_01</PassengerRef> <ServiceDefinitionRef SegmentRef="IB042620240108">SPECIAL_NEED-BLND</ServiceDefinitionRef> </OrderItem>Service> </OrderItems>OrderItem> |
And the OrderItem is linked to the ServiceDefinition where the service is again described.:
Code Block | ||
---|---|---|
| ||
<DataLists> <...> <ServiceDefinitionList> <...> <ServiceDefinitionList> <ServiceDefinition ServiceDefinitionID="SPECIAL_NEED-BLND"> <Name>Blind Passenger</Name> <Descriptions> <Description> <Text>Request<Text>Please Servicesupply Animalsecurity ifinstructions travellingin with one<braile</Text> </Description> <Description refs="ADULT_01"> <Text>Please supply security instructions in braile</Text> </Description> <Text>Solicite servicio de animales si viaja con uno</Text> <Description refs="ADULT_02"> <Text>Please supply security instructions in braile</Text> </Description> </Descriptions> <BookingInstructions> <SSRCode>BLND</SSRCode> </BookingInstructions> </ServiceDefinition> </ServiceDefinitionList> </DataLists> |
Specifically, the SSRCode
represents the special service request this example is making reference to. As shown in the table above, all codes have a 4-charcater length.
The ServiceDefinitionRef
contains the code for blind passengers SPECIAL_NEED-BLND
.
In the ServiceDefinitionList
further details regarding the SSR can be found.
...
In the ServiceDefinitionList
the additional information provided is reflected back to you, together with the BookingInstructions
needed by legacy systems.
Any Special Services not available through NDC should be made requested through ServIberia at least 48 hours before the flight.
IMPORTANT NOTE
Under no circumstances should the contents of any refs or ID’s be used to identify the type of service being offered/given. In the case of Ancillaries the RFIC and SubCode(RFISC) decoded against the ATPCo Optional Services Industry Sub Codes should be used, and in the case of Special Service Requests, the SSRCode should be used, decoded against the IATA Airimp or the above table, or you can simply use the <Name>
.
Rejection
If the special service is not available, due to inventory limits then the OrderCreate will be rejected, indicating the unavailable flight, with the following error:
...
...
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:
Code Block |
---|
<MediaList> <Media ListKey="Legal-Information"> <MediaLink>http://www.iberia.com/gb/legal-information/?language=en</MediaLink> </Media> <Media ListKey="Cabin-features"> <MediaLink>https://www.iberia.com/es/a-new-concept-in-flying/</MediaLink> </Media> <Media ListKey="Media-Checked-Baggage"> <MediaLink>https://www.iberia.com/IATAes/NDC/SecurePayment/2017.2"> <Document> <ReferenceVersion>5.000</ReferenceVersion> </Document> <Errors> <Error ShortText="SSE_RES_1001" Code="486">Servicio WCHS (Wheelchair for Steps) no disponible para IB0438-MAD-BIO-17JAN24. Reserva no admitida.</Error> </Errors> </OrderViewRS> </soap:Body> </soap:Envelope>luggage/allowance-in-hold/</MediaLink> </Media> <Media ListKey="Special-Needs"> <MediaLink>https://www.iberia.com/es/fly-with-iberia/special-needs/</MediaLink> </Media> </MediaList> |
Examples of messages with complete flows can be downloaded from here.
...