Skip to main content

Corporate Travel Services

v1
Corporate
Reservation
REST API
Try now
release_note
  • The 19.09 update to the Corporate Travel Services adds hotel payment information to the GET /travelers response, addresses an issue with the new Booking Connectivity Service (BCS), and includes additional handling when using Strong Customer Authentication (SCA).
  • The GET /travelers response now identifies the preferred payment card for hotel payment cards (under preferences), and includes hotel card summary information (under paymentCards). This information can be used to distinguish between user-assigned profile card preferences vs. default preference assignments, in situations where the profile synchronization process creates such default assignments.
  • New error messages have been added for the following error situations associated with Strong Customer Authentication (SCA):
  • The paymentAuthenticationReturnUrl is missing in the POST /carts/{id}/booking request, when this element is required by the mayRequirePaymentAuthentication indicator in the GET /carts response. The new error is type = "MISSING_PAYMENT_AUTHENTICATION_RETURN_URL" under category "MISSING_DATA" with description of "Booking cannot be made. In order to make a booking, payment authentication return url is required.".
  • When payment authentication fails because an error is returned by TravelFusion, or when an attempt is made to resume a booking with PATCH /bookings for a booking that was not pending authentication or has failed authentication. These situations return error type = "PAYMENT_AUTHENTICATION_FAILED" under category "INVALID_DATA" with description of "Booking cannot be made. Payment hasn't been successfully authenticated.".
  • Note: More information about Strong Customer Authentication (SCA) can be found in the Release Notes for 19.07 and 19.08.
  • An issue with the new Booking Connectivity Service (BCS) has been corrected. This problem was around handling the ticketing time limit for bookings made from the Corporate Travel Services (CTS), specifically with the POST /carts/{id}/bookings endpoint. Now bookings made with BCS are handled properly, clearing the way to switch ticketing to BCS.

API Information

Response Format
JSON
Method/Endpoint
*
Current Version
1.19.09
Target Audience
TN
Environment
Prod

What's New

  • The 19.09 update to the Corporate Travel Services adds hotel payment information to the GET /travelers response, addresses an issue with the new Booking Connectivity Service (BCS), and includes additional handling when using Strong Customer Authentication (SCA).
  • The GET /travelers response now identifies the preferred payment card for hotel payment cards (under preferences), and includes hotel card summary information (under paymentCards). This information can be used to distinguish between user-assigned profile card preferences vs. default preference assignments, in situations where the profile synchronization process creates such default assignments.
  • New error messages have been added for the following error situations associated with Strong Customer Authentication (SCA):
  • The paymentAuthenticationReturnUrl is missing in the POST /carts/{id}/booking request, when this element is required by the mayRequirePaymentAuthentication indicator in the GET /carts response. The new error is type = "MISSING_PAYMENT_AUTHENTICATION_RETURN_URL" under category "MISSING_DATA" with description of "Booking cannot be made. In order to make a booking, payment authentication return url is required.".
  • When payment authentication fails because an error is returned by TravelFusion, or when an attempt is made to resume a booking with PATCH /bookings for a booking that was not pending authentication or has failed authentication. These situations return error type = "PAYMENT_AUTHENTICATION_FAILED" under category "INVALID_DATA" with description of "Booking cannot be made. Payment hasn't been successfully authenticated.".
  • Note: More information about Strong Customer Authentication (SCA) can be found in the Release Notes for 19.07 and 19.08.
  • An issue with the new Booking Connectivity Service (BCS) has been corrected. This problem was around handling the ticketing time limit for bookings made from the Corporate Travel Services (CTS), specifically with the POST /carts/{id}/bookings endpoint. Now bookings made with BCS are handled properly, clearing the way to switch ticketing to BCS.

Relase note ID: 13361


  • The 19.08 update to the Corporate Travel Services corrects some issues with Bargain Finder Max (BFM - an upgrade to the Sabre flight shopping service). It also eliminates some confusion around baggage information in the Catalog and Cart; and it adds support for the Strong Customer Authentication (SCA) initiative in Europe.
  • Strong Customer Authentication (SCA) is a requirement of the EU Revised Directive on Payment Services (PSD2) affecting payment service providers within the European Economic Area. The SCA requirement is expected to come into force starting 14 September 2019.
  • The two new fields added to support SCA in the 19.07 release are now functional: the boolean indicator `mayRequirePaymentAuthentication` in the `GET /carts` response and the `paymentAuthenticationReturnUrl` element in the `POST /carts/{id}/bookings` request. (See the [19.07 Release Notes](http://corporatetravel.developer.sabre.com/changelog/1907-release-notes#section-strong-customer-authentication-sca) for more details.)
  • After the traveler returns from authentication a `PATCH /bookings` request needs to be submitted with `finalizeBooking` = "true". This tells the system to resume polling to check for a response to the original booking request; testing to see if the booking is complete. The service will respond by returning `status` = "204".
  • Also, the following error messages have been added to support SCA:
  • Traveler tries to resume a booking without completing payment authentication. The error is `type` = "PAYMENT_AUTHENTICATION_FAILED" under `category` "INVALID_DATA" with the `description` "Payment hasn't been successfully authenticated."
  • If `paymentAuthenticationUrl` is not included in the `POST /carts/{id}/bookings` request when required (i.e., when `mayRequirePaymentAuthentication` is `true` in the `GET /carts` response). This error is `type` = "MISSING_PAYMENT_AUTHENTICATION_RETURN_URL" under `category` "MISSING_DATA" with a `description` of "In order to make a booking, payment authentication return url is required."

API Information

Response Format
JSON
Method/Endpoint
*
Current Version
1.19.08
Target Audience
TN
Environment
Prod

What's New

  • The 19.08 update to the Corporate Travel Services corrects some issues with Bargain Finder Max (BFM - an upgrade to the Sabre flight shopping service). It also eliminates some confusion around baggage information in the Catalog and Cart; and it adds support for the Strong Customer Authentication (SCA) initiative in Europe.
  • Strong Customer Authentication (SCA) is a requirement of the EU Revised Directive on Payment Services (PSD2) affecting payment service providers within the European Economic Area. The SCA requirement is expected to come into force starting 14 September 2019.
  • The two new fields added to support SCA in the 19.07 release are now functional: the boolean indicator `mayRequirePaymentAuthentication` in the `GET /carts` response and the `paymentAuthenticationReturnUrl` element in the `POST /carts/{id}/bookings` request. (See the [19.07 Release Notes](http://corporatetravel.developer.sabre.com/changelog/1907-release-notes#section-strong-customer-authentication-sca) for more details.)
  • After the traveler returns from authentication a `PATCH /bookings` request needs to be submitted with `finalizeBooking` = "true". This tells the system to resume polling to check for a response to the original booking request; testing to see if the booking is complete. The service will respond by returning `status` = "204".
  • Also, the following error messages have been added to support SCA:
  • Traveler tries to resume a booking without completing payment authentication. The error is `type` = "PAYMENT_AUTHENTICATION_FAILED" under `category` "INVALID_DATA" with the `description` "Payment hasn't been successfully authenticated."
  • If `paymentAuthenticationUrl` is not included in the `POST /carts/{id}/bookings` request when required (i.e., when `mayRequirePaymentAuthentication` is `true` in the `GET /carts` response). This error is `type` = "MISSING_PAYMENT_AUTHENTICATION_RETURN_URL" under `category` "MISSING_DATA" with a `description` of "In order to make a booking, payment authentication return url is required."

Business Value

  • Bargain Finder Max (BFM) is an enhanced version of Sabre's Intellisell flight shopping webservice. Two issues have been corrected that prevented Corporate Travel Services from upgrading to BFM from an older version of Intellsell. Now that these problems have been resolved the `POST /catalogs` service will switch to BFM with this release.

Resolved Issues

In the Request/Response

Required

* A problem with 24-hour shopping has been fixed. Now when a `POST /catalogs` request includes `hoursTolerance` = "12" flights will be returned from the entire day. And when `hoursTolerance` is specified as any other value (an integer from 0-11), flights will be returned using a time window based on the `departTime` (or `time`) included in the request, plus and minus the `hoursTolerance` value. (Remember that a time window can be constructed which crosses midnight, but flights from any other day will not be included in the response.)

* The mapping for `cabinTypeName` has been updated. Now flights in the `GET /catalogs` response specify the correct class of service. Changes noted for `POST /catalogs` also apply to `alternativeFlightItineraries` in the `GET /carts` response, when using `shopByTime`.

A problem with baggage information has been addressed for flights from the Sabre GDS in the `GET /catalogs` response (and in the `alternativeFlightItineraries` section of the `GET /carts` response). The `firstPiece` and `lastPiece` elements under `freeTextPolicy` have been removed to avoid confusion. These parameters are only used with paid bags (not yet supported), and have no meaning for free bags. Remember that baggage information is only available from Sabre when shopping is done using Bargain Finder Max (BFM).

Relase note ID: 13360


  • Better categorization and additional information has been added for the following error situations:
  • Traveler age is too young on Agentware. The new error is `type` = "TRAVELER_TOO_YOUNG" under `category` "INVALID_DATA" with `description` of "Booking cannot be made. Traveler must be 12 years of age or older.".
  • Connection time between flights is too short. This is error `type` = "INSUFFICIENT_CONNECTING_TIME" under `category` "INVALID_DATA" with `description` of "Insufficient connecting time between journeys".
  • Other updates have been made to improve various Corporate Travel Services:
  • Fixed an issue with the currency of `quotedPrice` for seats under `AirExtras` in the `GET /seatmaps` and `GET /carts responses`.
  • The voucher amount debited has been corrected in the `GET /bookings` response, in the `appliedVouchers` section. Previously there was an issue with the implied decimal location, so a value of `20400` was shown as `204`, for example.
  • SCA is a requirement of the EU Revised Directive on Payment Services (PSD2) affecting payment service providers within the European Economic Area. The SCA requirement is planned to come into force starting 14 September 2019.
  • In preparation for SCA new fields have been added to the CTS APIs. These new items are present in the 19.07 release, but are not active (functional) and will not be required until 19.08:
  • A boolean indicator `mayRequirePaymentAuthentication` has been added to the `GET /carts` response. When this is true it means the Cart includes a Travelfusion itinerary and SCA may be in effect.
  • The element `paymentAuthenticationReturnUrl` has been added to the `POST /carts/{id}/bookings` request. This is the URL to which the traveler will be redirected after they have completed the authentication process. This new element is at the same level as `components` and `travelers` in the request. Starting in 19.08 a value needs to be provided for this element whenever `mayRequirePaymentAuthentication=true` in the Cart.

API Information

Response Format
JSON
Method/Endpoint
*
Current Version
1.19.07
Target Audience
TN
Environment
Prod

What's New

  • Better categorization and additional information has been added for the following error situations:
  • Traveler age is too young on Agentware. The new error is `type` = "TRAVELER_TOO_YOUNG" under `category` "INVALID_DATA" with `description` of "Booking cannot be made. Traveler must be 12 years of age or older.".
  • Connection time between flights is too short. This is error `type` = "INSUFFICIENT_CONNECTING_TIME" under `category` "INVALID_DATA" with `description` of "Insufficient connecting time between journeys".
  • Other updates have been made to improve various Corporate Travel Services:
  • Fixed an issue with the currency of `quotedPrice` for seats under `AirExtras` in the `GET /seatmaps` and `GET /carts responses`.
  • The voucher amount debited has been corrected in the `GET /bookings` response, in the `appliedVouchers` section. Previously there was an issue with the implied decimal location, so a value of `20400` was shown as `204`, for example.
  • SCA is a requirement of the EU Revised Directive on Payment Services (PSD2) affecting payment service providers within the European Economic Area. The SCA requirement is planned to come into force starting 14 September 2019.
  • In preparation for SCA new fields have been added to the CTS APIs. These new items are present in the 19.07 release, but are not active (functional) and will not be required until 19.08:
  • A boolean indicator `mayRequirePaymentAuthentication` has been added to the `GET /carts` response. When this is true it means the Cart includes a Travelfusion itinerary and SCA may be in effect.
  • The element `paymentAuthenticationReturnUrl` has been added to the `POST /carts/{id}/bookings` request. This is the URL to which the traveler will be redirected after they have completed the authentication process. This new element is at the same level as `components` and `travelers` in the request. Starting in 19.08 a value needs to be provided for this element whenever `mayRequirePaymentAuthentication=true` in the Cart.

Relase note ID: 13362