Release Note 21-01-20

NDC API 21-01-2020

Selling and Content

Revised Commission Logic (Selling Flow)

 Effective Date:
    
 APIs Affected:

17.2 OrderCreate, 17.2 OrderChange (Confirm Held Booking), 16.1 OrderCreate and 16.1 OrderChange (Confirm Held Booking)

New Feature

Revised Commission Logic extends commission calculation and applicability on Orders created using Private Fares. So far, commission was only applied for Public Fares which was calculated using commission tables residing in NDC database.

Going forward with the release, commission will be applied for following scenario

  1. Private Fare – If there is a Private Fare filed with a specific commission value (zero/non-zero), commission will be applied as per the value
  2. Public Fares – Commission will continue to be calculated on Public Fares as it is done at present
  3. Long Haul APP Fares – Commission will start getting calculated and applied for these fares after the change implementation
  4. Short Haul APP Fares – Commission will start getting calculated and applied for these fares after the change implementation.

Please note, since the changes are not affecting Request/Response interface or Service definition, there are not any amendments to technical specification pages.

 Critical Impact:

LOW - This change will not be a breaking change to consumers of the British Airways NDC APIs

 Batch Release:
 R339

Voluntary Servicing

Error Handling for Auto Cancelled Bookings

 Effective Date:
   
 APIs Affected:

16.1 and 17.2 Servicing APIs

 Problem/Issue

This is to fix a bug where 16.1 and 17.2 Servicing API’s displays an irrelevant error message while retrieving a held booking, which is auto cancelled due to non-payment within ticketing time limit.

 Solution

16.1 and 17.2 Servicing APIs will display a more appropriate error message to say that booking has been cancelled.

Please click on the relevant API to see the specific error response message.

  1. SeatAvailability
  2. Passenger Servicing
  3. Ancillary Servicing
  4. OrderCancel
  5. ServiceList
  6. Change Booking - Reprice
  7. Change Booking - Reshop
  8. Confirm Held Booking
  9. Confirm Change Booking
  10. Refund Quote
  11. Requote Held Booking
  12. Split Booking

 Batch Release IT Ref:
R339 - NDCAVS-568

Cooling Off Period

 Effective Date:
   
 APIs Affected:

16.1 ItinReshop, 16.1 OrderCancel, 17.2 OrderReshop and OrderCancel APIs

New Feature

NDC offers cooling-off period for ticketed bookings and allows them to be cancelled for free if they are cancelled within cooling-off period. This enhancement is to change the NDC cooling-off period policy based on the below three rules:

  1. Up to 24 hours after booking creation.
  2. Until 23:59 of the ticketing location.
  3. Up to -24 hours of the first flight STD.

Cooling off period time limit is calculated by comparing Rule 1 & 2 to choose more generous one and then comparing the generous value with Rule 3 to derive the more restrictive one, which would be the final cooling-off period.

E.g. 1: If an instant purchase booking is made at 13:00 today, then cooling off period is applicable till 12:59 tomorrow.

E.g. 2: If a held booking is made at 13:00 today and payment is made at 12:00 tomorrow, then cooling off period is applicable till 23:59 tomorrow.

E.g. 3: If a held booking is made at 13:00 today and payment is made at 14:00 tomorrow, then cooling off period is applicable till 23:59 tomorrow.

For Rule 3, If the first flight STD-24 hours is within the cooling off period of the booking then cooling off period time limit should be reduced to STD-24 hours.

E.g. 4: If an instant booking is made at 13:00 today for a flight which departs at 21:00 tomorrow, then cooling off period is applicable till 20:59 today.

Restrictions:

  • Split bookings and reissued booking will be ineligible for cooling-off period.

NB These are business logic changes and hence no development changes are needed.

 Critical Impact:

LOW - This change will not be a breaking change to consumers of the British Airways NDC APIs

 Batch Release:
 R339

Booking commission correction

 Effective Date:
   
 APIs Affected:

16.1 OrderCreate and 17.2 OrderCreate

 Problem/Issue

This is to fix a bug in OrderCreate API where incorrect commission amount was added to the booking on a few cases when the booking has more than one Origin/Destination.

 Solution
Commission will be added correctly for such journeys.
 Batch Release IT Ref:
R339 - NDCD-38

Passenger name corrected in the email sent to agent, corporate and customers. 

 Effective Date:
   
 APIs Affected:
16.1 Orderchange and 17.2 OrderChange
 Problem/Issue

This is to fix a bug where the incorrect passenger name was sent in the email sent to agent, corporate or customers on successful purchase of seats and meals via NDC channel.

 Solution
The mail will be sent to the agent, corporate or customer with the correct passenger name for seat and meal purchase.
 Batch Release IT Ref:
R339 - NDCD-46

Agents from Israel will be able to successfully cancel the private fare bookings.

 Effective Date:
   
 APIs Affected:
16.1 OrderCancel and 17.2 OrderCancel
 Problem/Issue

This is to fix a bug in OrderCancel API where cancellation attempt of bookings (mainly private fare bookings) made by Israeli agents returned error.

 Solution
Agents from Israel will be able to successfully cancel the private fare bookings.
 Batch Release IT Ref:
R339 - NDCD-41

NDC Waivers and Favours

 Effective Date:
   
 APIs Affected:

17.2 OrderReshop, 17.2 OrderChange and 17.2 OrderCancel (Also fix for 16.1 Servicing APIs)

New Feature

The waivers and favours capability allows travels agents to request and avail waivers on certain ticket sales and servicing rules.

Waivers would be granted based on a request which is approved by the travel agency account manager.

The agent is then expected to send a request for ticket sell or servicing as normal and the system would automatically apply the appropriate waiver based on the approval.

The following types of waivers are currently supported within NDC:

  • Ticketing Time Limit Waiver
  • Cancellation Fee Waiver
    • Valid only up to 72 hours after addition to PNR
  • Full Refund Waiver
    • Valid only up to 72 hours after addition to PNR
 Critical Impact:

LOW - This change will not be a breaking change to consumers of the British Airways NDC APIs

 Batch Release:
 R339 - NDCAVS-1121