Hotels API

Facilities

The hotel and room facility catalogues, with icon classes, priorities and translated labels. Use them to build amenity filters and your icon mapping.

Two catalogues list the facilities: one for hotels, one for rooms. Datasheets carry facilities in the same shape, in accommodationFacilities[] and roomFacilities[]. Fetch each catalogue once per language and sync run.

The path is spelled facilites (sic)Spec

Both paths really are /facilites/..., not /facilities/.... lang is required on both.

Accommodation facilities

GET/facilites/accommodation

Request

Headers

auth-tokenstringrequiredDocs
Any valid token. Static content doesn't need the booking-flow token.
Accept-EncodingstringrequiredDocs
gzip

Query

langLanguagerequiredSpec
Language of the labels, for example EN.

Response

200 OK

facilities[]AccommodationFacilityVO[]Spec

Every hotel facility.

Child attributes
idinteger
Facility id.
iconstring
A CSS class, for example fa-regular fa-grill or ico-tc-SPA. Map it to your own icon set.
priorityinteger
Higher means more prominent.
translationsobject
Map of language to label.

This response has no auditData and no Travelc-Trace-Id header. Tested For support, keep the full request and response in your logs, with the token redacted. Confirmed Log the x-request-id response header too.

Room facilities

GET/facilites/room

Request

Headers

auth-tokenstringrequiredDocs
Any valid token.
Accept-EncodingstringrequiredDocs
gzip

Query

langLanguagerequiredSpec
Language of the labels, for example EN.

Response

200 OK

facilities[]RoomFacilityVO[]Spec

Every room facility: the same fields as a hotel facility, plus category.

Child attributes
idinteger
Facility id.
iconstring
A CSS class.
priorityinteger
Higher means more prominent.
translationsobject
Map of language to label.
categoryenum
One of the room facility categories, for example BATHROOM.

This response has no auditData and no Travelc-Trace-Id header. Tested For support, keep the full request and response in your logs, with the token redacted. Confirmed Log the x-request-id response header too.

Room facility categories

RoomFacilityVO.category takes one of 12 values. Spec

GENERAL, ACTIVITIES, BATHROOM, MEDIA_AND_TECHNOLOGY, FOOD_AND_DRINK, INTERNET, KITCHEN, OUTDOORS, VIEW, LIVING_AREA, BEDROOM, EXCLUSIVE_SERVICES

Sorting and icons

  • Sort by priority, highest first, to pick "top amenities" for a hotel card or page.
  • icon is a CSS class: Font Awesome (fa-regular fa-…) or the platform's own ico-tc-… classes. Map it to your own icon set.
  • Whether a facility costs extra is not specified. Docs
  • The facility data is dynamic. Docs Refresh both catalogues on every sync run; they are small.
Top six amenities for a hotel page
const top = [...sheet.accommodationFacilities]
  .sort((a, b) => b.priority - a.priority)
  .slice(0, 6)
  .map((f) => ({ label: f.translations[lang], icon: iconFor(f.icon) }));

Legacy shapes

DeprecatedSpec

The legacy facilities node and /facilities endpoint are deprecated. Use accommodationFacilities[] and roomFacilities[].

Old docs and samples also show facilities { includedFacilities[], nonIncludedFacilities[], otherFacilities[] } and plain-string lists such as includedServices[]. Don't build on them.

Preferred hotels

The hotels your microsite promotes, returned as full datasheets. Use them for landing pages and recommended rails, then quote them for prices.

Meal plans

The meal plans configured on your microsite, with their codes, types and descriptions. Use them to label the mealPlan codes you get from Quote.