...
| Table of Contents | ||||
|---|---|---|---|---|
|
...
Some services are not accepted by our code-share partners, and therefore may be rejected.
Note: The inclusion of SSRs can only be done in the initial creation of the Order and not added later in a Servicing flow.
...
| Code Block |
|---|
<Qualifier> <SpecialNeedQualifiers> <Code>BLND</Code> </SpecialNeedQualifiers> </Qualifier> |
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 |
|---|
...
Any Special Services not available through NDC should be 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>.
...
Examples of messages with complete flows can be downloaded from here.
...