AY NDC specificities
For 21.3 seller recognition specificities, please check the 21.3 implementation guide for shared features and the DistributionChain example on page 5. In 21.3 SystemID is replaced by OrgID.
Assuming you have already implemented another Altea carrier, you are quite likely aware of “Agency Handling” / “Seller Recognition” / “NDC Configuration”. These are various names for the same feature: a way to identify the seller in our API. See a detailed guide for this part.
Seller recognition is mandatory in our API, and we do require the sending of either IATA or TIDS number.
The fare rules and benefits enable communication of the label and the value mapping, which can be used to receive content in given languages for different fare families. Here is described the process and added a complete Fare Rules and Benefits list.
Files for fare rules and benefits labels: Labels.xlsx and Labels.json
Check our release note on how to use private fares in Finnair NDC.
Learn more about different private and published fare types available in Finnair on the Fares & Rules page.
Partners implementing NDC with Finnair (any version) can currently only implement OrderChangeNotification message v18.1 (OCN v21.3 not available yet). OCN v18.1 will work even if all other aspects of the implementation were done with v21.3.
Finnair uses OCN codes from CHT (change type) and CHR (reason for change) IATA codesets:
CHT | CHR |
| 1 - flight number change | 104 - order cancelled due to TTL expiry |
| 2 - flight retimed | 112 - change requested by passenger |
| 3 - flight cancelled | 113 - passenger no-show at gate |
| 6 - ancillary or flight status changed | 116 - other (if other codes are not suitable) |
| 9 - passenger name modified | |
| 11 - passenger contact details updated | |
| 13 - OrderItem cancelled | |
| 18 - OrderItem added | |
| 19 - Frequent flyer information updated | |
| 20 - Identity document details updated |
If multiple changes occur simultaneously, then only the highest priority OCN will be sent:
OCN codes priorities - decreasing from left to right:
1 > 2 > 3 > 104 > 113 > 112 > 6 (flight status change) > 18 > 6 (ancillary change) > 13 > 9 > 11 > 19 > 20 > 116
In prime booking flow, it is mandatory to send an OfferPrice message before the SeatAvailability. Otherwise, the seat prices and possible exemptions may not be applied correctly, and the booking can fail.
Secure flights require passport information and date of birth for boarding.
Passport information can be added during OrderCreate message, we recommend implementing this step as mandatory however the passport information can be also added or updated during check-in.
While the Altea NDC API itself doesn’t enforce them, these contact-related fields are all mandatory for AY bookings:
- Phone number (AP)
- Email address (APE)
- Notification contact (APN/CTCE/CTCM)
- Billing address, for credit card payments (AB)