Skip to main content

Get Hotel Content

3.0
Hotel
Search
REST API
Try now
release_note
  • 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
  • Schema changes to support ability to AAA into a different PCC in the future
  • Renamed 'PointOfInterests' to 'PointsOfInterest'

API Information

Response Format
JSON
Method/Endpoint
GetHotelDetailsRQPOST /v3.0.0/get/hotelcontent
Current Version
3.0.0
Target Audience
TN
Environment
Production

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
  • Schema changes to support ability to AAA into a different PCC in the future
  • Renamed 'PointOfInterests' to 'PointsOfInterest'

New Features

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
Parameter: POS

Type: object

Description: Allows user to AAA into a different PCC

Sample Value:

"POS": {
	"Source": {
		"PseudoCityCode": "TM61"
	}
}
Note: This is added to schemas as a future enhancement. Current functionality does not support this.

In the Response

Optional

Parameter: SabreHotelCode

Type: string

Description: Sabre Hotel Code of a Global ID.

Sample Value:

53121
Note: Populated only if a Global ID has a Sabre Hotel Code mapped to it, and the search was made with the Global ID
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"
	 }
  ]
}
Note:

Functional Updates And Enhancements

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": true
Note: This is changed from 'PointOfInterests' to 'PointsOfInterest' in the V3.0.0 schemas

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

Relase note ID: 13355