v3.0.0 | June 1, 2020
- Content Services for Lodging APIs now provide the ability to search for and identify properties that have implemented enhanced safety protocols to provide a safe stay for the guests
- A new amenity OTA code (2002) can be used to request and identify properties that support the Stay Safe initiative
- For more information - https://developer.sabre.com/docs/safe_stay_indicator
API Information
What's New
- Content Services for Lodging APIs now provide the ability to search for and identify properties that have implemented enhanced safety protocols to provide a safe stay for the guests
- A new amenity OTA code (2002) can be used to request and identify properties that support the Stay Safe initiative
- For more information - https://developer.sabre.com/docs/safe_stay_indicator
Business Value
- In the wake of the COVID-19 crisis, hotels around the globe are increasingly looking at improving cleanliness programs at their properties. Hotels want to provide guests with peace of mind and assure them that their room has been thoroughly sanitized. Whether it's guest rooms, restaurants, gyms, or other public areas, hotels want to make sure the health and safety of guests is a priority, now more than ever.
- While our hotel partners have always taken providing clean rooms seriously, some are taking actions that go above and beyond standards provided by various governing bodies to meet the expectations presented by COVID-19. Several hoteliers are already implementing enhanced hotel cleaning practices, social interactions, and workplace protocols to meet new health and safety regulations.
- This is of particular importance as Sabre connected travel agencies, Online Travel Agencies (OTAs), and corporations have a duty of care about the well-being of the traveler whilst they are on their trip
New Features
In the Response
Optional
- Parameter: Amenities
-
Type: String
Description: The Stay Safe indicator is returned as Amenities as Code 2002 in the API response for the properties that support Stay Safe guidelines.
Sample Value:
"Amenities": {
"Amenity": [
{
"Code": 2002,
"Description": "Stay Safe",
"value": ""
},
{
"Code": 262,
"Description": "Kitchenette",
"value": ""
},
{
"Code": 42,
"Description": "Free parking",
"value": ""
},
{
"Code": 44,
"Description": "Game room",
"value": ""
},
{
"Code": 55,
"Description": "Hot Tub",
"value": ""
}
]
}
v3.0.0 | November 13, 2019
- The response now shows both the Sabre Hotel Code and the Global ID
- Added ability to view Security Features mapped to a property
- Amenities can now have a text description assosciated to them
- Added ability to shop in an authorized (AAA Access) branch location (PCC) while remaining signed-into the home branch or IPCC
- Renamed 'PointOfInterests' to 'PointsOfInterest'
API Information
What's New
- The response now shows both the Sabre Hotel Code and the Global ID
- Added ability to view Security Features mapped to a property
- Amenities can now have a text description assosciated to them
- Added ability to shop in an authorized (AAA Access) branch location (PCC) while remaining signed-into the home branch or IPCC
- Renamed 'PointOfInterests' to 'PointsOfInterest'
New Features
In the Response
Optional
- Parameter: SabreHotelCode
-
Type: string
Description: Sabre Hotel Code of a Global ID.
Sample Value:
53121Note: Populated only if a Global ID has a Sabre Hotel Code mapped to it, and the search was made with the Global ID
In the Request
Optional
- Parameter: SecurityFeatures
-
Type: boolean
Description: Boolean field to control whether you want to see security features in the response
Sample Value:
"SecurityFeatures": "false"Note: Default false. When true, Security feature information is returned in the response
In the Response
Optional
- Parameter: SecurityFeatures
-
Type: object
Description: Security features (mapped to SEC OTA Code) applicable to a property
Sample Value:
"SecurityFeatures":{
"SecurityFeature":[
{
"Code":9,
"Description":"Complies with Local/State/Federal fire laws",
"value":"Fire safety law compliant"
}
]
}
In the Request
Optional
- Parameter: POS
-
Type: object
Description: Allows shopping in an authorized (AAA Access) branch location (PCC) while remaining signed-into the home branch or IPCC
Sample Value:
"POS": {
"Source": {
"PseudoCityCode": "TM61"
}
}Note: Although the shopping happens in the branch location PCC given in the request, the underlying Session or Token used to authenticate or call this API remains unchanged. This is different from how AAA branch shopping worked in legacy GDS where the underlying session itself is AAAed into the branch location
Functional Updates And Enhancements
In the Response
Optional
- Parameter: Amenities
-
Type: object
Description: Amenities available at the property
Sample Value:
"Amenities": {
"Amenity": [
{
"Code": 15,
"Description": "Car rental desk",
"ComplimentaryInd": false,
"value": "Ask at reception for car rental charges"
}
]
}Note: Amenities can now have text information assosciated to an Amenity
In the Request
Optional
- Parameter: PointsOfInterest
-
Type: boolean
Description: Boolean flag to control whether points of interest should be returned in the API response
Sample Value:
"PointsOfInterest": trueNote: This is changed from 'PointOfInterests' to 'PointsOfInterest' in the V3.0.0 schemas