Skip to main content

Booking Management API - Beta

Trip Management
Booking
REST API
Travel Agency
Try Now

Beta Release - Use for test purpose only - Work in progress

This API is for testing purposes only. For the full version, please navigate to the Booking Management API.
release_note
  • Modify Booking will now support modification of the traveler details stored in the booking (name, surname, phone and email information, frequent flyer loyalty details) for traditional content (e.g.: ATPCO flights).
  • Added support for adding and updating the travel agency customer identifier (DK number).
  • Support for modifying group bookings was implemented in the Modify Booking. Customers will be able to adjust the traveler list associated with the group.
  • Added support for the modification of the special service requests (SSRs).

API Information

Response Format
JSON
Method/Endpoint
/v1/trip/orders/
Current Version
1.15
Target Audience
TN
Environment
Production

What's New

  • Modify Booking will now support modification of the traveler details stored in the booking (name, surname, phone and email information, frequent flyer loyalty details) for traditional content (e.g.: ATPCO flights).
  • Added support for adding and updating the travel agency customer identifier (DK number).
  • Support for modifying group bookings was implemented in the Modify Booking. Customers will be able to adjust the traveler list associated with the group.
  • Added support for the modification of the special service requests (SSRs).

Business Value

  • Customers can now modify traveler information stored in the traditional content booking. Modification of the traveler’s name and surname, full control over the contact details (phones and emails) as well as frequent flyer data are now possible.
  • Additional logic was implemented to let customers add and update the travel agency customer identifier (DK number).
  • Modify Booking will now support group booking modification. Customers can verify traveler’s assignation within a group, add, update and delete this data as they wish (having potential airline restrictions in mind).
  • The first iteration of the SSR modification was released (limited functionality). It includes automatic infant SSR handling when associated infant traveler information is changed.

New Features

In the Request

Optional

Parameter: ModifyBookingRequest.after.agencyCustomerNumber

Type: String

Description: The travel agency customer identifier also known as customer number or DK number. Can be a six, seven or 10-character string.

Sample Value:

"after": {
        "agencyCustomerNumber": "1234567",
        "travelers": [
            {
                "givenName": "JOHN",
                "surname": "DOE",
                "birthDate": "1970-01-23",
                "passengerCode": "ADT"
            }
        ]
    }
Note: Delete operation is not supported.

In the Request

Optional

Parameter: ModifyBookingRequest.after.travelers.isGrouped

Type: Boolean

Description: ModifyBookingRequest.after.travelers.isGrouped

Sample Value:

"after": {
        "travelers": [
            {
                "givenName": "JOHN",
                "surname": "BROWN",
                "birthDate": "1970-01-23",
                "passengerCode": "ADT",
 "isGrouped": true
            }
        ]
    }
Note:

In the Request

Optional

Parameter: ModifyBookingRequest.after.travelers.loyaltyPrograms.tierLevel

Type: Integer

Description: The level reached by the traveler in the loyalty program.

Sample Value:

"after": {
        "travelers": [
            {
                "givenName": "JOHN",
                "surname": "DOE",
                "passengerCode": "ADT",
                "loyaltyPrograms": [
                    {
                        "supplierCode": "BA",
                        "programType": "FREQUENT_FLYER",
                        "programNumber": "002001557133700",
                        "tierLevel": 2,
                        "receiverCode": "BA"
                    }
                ]
            }
        ]
    }
Note: Additional properties `tierLevel` and `receiverCode` were added to support frequent flyer programs for the traditional content.

In the Request

Optional

Parameter: ModifyBookingRequest.after.specialServices

Type: Array

Description: Lists all special service request (SSR) messages sent to an airline. The messages may contain traveler preferences or mandatory/optional information directed to the airline.

Sample Value:

"after": {
        ...
        "specialServices": [
            {
                "travelerIndices": [
                    1
                ],
                "code": "BLND"
            }
        ]
    }
Note: Limited functionality of the SSR modification was added. Refer to the Help section of the BM API Beta documentation for more details.

Functional Updates And Enhancements

In the Request

Optional

Parameter: ModifyBookingRequest.after.travelers.phones

Type: Array

Description: Lists all phone numbers associated with the traveler.

Sample Value:

"after": {
        "travelers": [
            {
                "givenName": "JOHN",
                "surname": "DOE",
                "birthDate": "1970-01-23",
                "passengerCode": "ADT",
 "phones": [
                    {
                        "number": "2025550137"
                    }
                ]
            }
        ]
    }
Note: Additional logic was added allowing modification of the `phones`, `emails` and `loyaltyPrograms` associated with travelers stored in the booking, in the case of traditional flight content.

In the Request

Required

Parameter: ModifyBookingRequest.after.travelers.birthDate

Type: String

Description: The date of birth of the traveler in YYYY-MM-DD format.

Sample Value:

        "travelers": [
            {
                "givenName": "JOE",
                "surname": "DOE",
                "birthDate": "2022-03-04",
                "passengerCode": "INF",
                "isGrouped": true
            }
        ]
Note: `birthDate` property is now required for infant travelers due to the implementation of the automatic INFT SRR logic.

Resolved Issues

In the Request

Optional

DE242077: Fixed a bug in the Modify Booking method where the lead guest information was not properly set for the CSL bookings.

Relase note ID: 17545


  • Additional improvements in terms of the error handling logic.

API Information

Response Format
JSON
Method/Endpoint
/v1/trip/orders/
Current Version
1.14
Target Audience
TN
Environment
Production

What's New

  • Additional improvements in terms of the error handling logic.

Business Value

  • Additional improvements in terms of the error handling logic.

Resolved Issues

In the Request

Optional

US1417169: Adding new error handling (BOOKING_NOT_FOUND) in the ModifyBooking method for a scenario where the specified booking ID has not been found.

Relase note ID: 17345


API Information

Response Format
JSON
Method/Endpoint
/v1/trip/orders/modifyBooking
Current Version
1.13
Target Audience
TN
Environment
Production

What's New

Business Value

  • The Modify Booking method is a part of Booking Management API and allows users to change their Sabre reservations/bookings in a better way. This API provides a set of properties to modify an existing booking. By having a normalized schema both expert and novice users can integrate and adopt Sabre APIs in the most seamless way possible.

Relase note ID: 17231