Rooms

The Rooms Query returns a static room list from a Supplier access, and may include translations to other languages.

This call is only useful for Suppliers that publish a static room master. Many Suppliers do not provide one because their room details are generated dynamically at Search time. In those cases, the Rooms Query may return limited data or no room list.

FastX does not provide a static room master list endpoint. Instead, FastX returns a standardized room code and description at Search time, based on each Supplier's native room values in the response.

The returned fields of the rooms query include:

• roomCode
• source
• occupancies
• amenities
• medias
• views
• beds

Query Overview

When creating your rooms query, you have two different inputs to fill based on your specific needs:

1. Criteria
2. Token

1. Criteria

This query offers versatility, with certain fields marked as mandatory (access) and others as optional (roomCodes). This flexibility empowers you to create a personalized Rooms Query, tailoring the requested fields to your specific needs. Consequently, the response will only include information that is highly relevant to you, streamlining the retrieval process and ensuring the data you receive meets your exact requirements.

{
	"criteria": {
		"access": "2",
		"maxSize": 5,
		"roomCodes": [
			"2269"
		]
	},
	"token": ""
}

Mandatory criteria

• access

Optional criteria

• roomCodes (Search by room type)
• maxSize (Paginate response)

2. Token

The HotelX API provides paginated responses to handle cases where the number of rooms from the selected provider exceeds 10000. The default response page contains a maximum of 500 rooms, but you can specify the number of objects returned per page using the maxSize field in the query criteria to retrieve between 1 and 10000 rooms.

To include the token in your request, all you need to do is:

1. Add the token object to the fields and arguments. Moreover, you have the flexibility to specify the number of objects returned per page by utilizing the maxSize tag in your arguments.

2. After receiving a response, you will only receive a portion of the full list. To access the next page, simply copy the token tag from the response and include it in your next request. This will allow you to obtain a new set of objects in the following response.

3. Repeat these steps until the token is no longer included in the response, which indicates that all available results have been retrieved.

Query variables

First, in your rooms query you won't indicate any tokeninput:

{
    "criteria" : {
        "access" : "2",
        "maxSize" : 5
    },
    "token" : ""
}

You will obtain a response with 5 rooms per page:

Response

{
	"data": {
		"hotelX": {
			"rooms": {
				"token": "FGluY2x1ZGVfY29udGV4dF91dWlkDnF1ZXJ5FGhlbkZldGNoAhZMN2w2SlZYaVNaaXhYeXHwdm1GWjlBAAAAAATLRLQWeXZ3cU12MkpSbTY3WkF6QzJraWJWZxZFX3NZYkQ1UFN6fWFaQjlXMXBSbmhBAAAAABCavEoWWFltUDMwVXRUT0ctUWY5Y3FDX39vQQ=="
				"edges": [

This token should be used as input in your next rooms query, inside the token input:

{
    "criteria" : {
        "access" : "2",
        "maxSize" : 5
    },
    "token" : "FGluY2x1ZGVfY29udGV4dF91dWlkDnF1ZXJ5FGhlbkZldGNoAhZMN2w2SlZYaVNaaXhYeXHwdm1GWjlBAAAAAATLRLQWeXZ3cU12MkpSbTY3WkF6QzJraWJWZxZFX3NZYkQ1UFN6fWFaQjlXMXBSbmhBAAAAABCavEoWWFltUDMwVXRUT0ctUWY5Y3FDX39vQQ=="
}

Response Considerations

note

The amount of information and content returned might vary between Sellers.

HotelX supports all languages, but receiving room descriptions in one or another depends entirely on the languages supported by the Seller.

Query Inputs

HotelXRoomQueryInput (INPUT_OBJECT)

access  *  (ID)

Indicates the access that you want use.

roomCodes(String)

Indicates the room codes that you want filter.

maxSize(Int)

Maxium number of items per page

token (String)
A unique authentication token required for API requests.

How FastX Room Standardization Works

Every FastX Search response includes FastX standardized room codes and descriptions alongside the Supplier's native values. This provides your system with unified room information across connected Suppliers.

This standardization is generated in real time during Search. It is not a static room catalog that you can retrieve in advance.

Standardization process

1. Supplier sends native room description during Search (for example, "Twin Deluxe with Sea View")
2. FastX analyzes the description in real time using an AI-based process
3. Standardized output generated: A uniform room code and normalized description
4. Both values returned: Original Supplier room code and description + FastX standardized room code and description

Detected room components

The model analyzes the Supplier's native room description and detects the following attributes:

• Category (Standard, Deluxe, Basic, etc.)
• Type (Room, Studio, Apartment, etc.)
• Capacity (Single, Twin, Double, Triple, etc.)
• Environment (Shared Bed, Women Only, etc.)
• View (Ocean, Sea, Park, Garden, etc.)
• Features (Jacuzzi, Air Conditioning, Kitchenette, etc.)
• Beds (Queen, Double, King, etc.)
• Bedrooms (1, 2, 3, etc.)

Example

Different Supplier descriptions can be standardized into the same FastX room code and description:

Supplier	Supplier Room Description	FastX Room Code	FastX Room Description
SUP1	Sea View Double Room (BB BAR FLEX)	str--AA--d--	Standard Double Room views Sea
SUP2	Sea View Double Room (RO BAR FLEX)	str--AA--d--	Standard Double Room views Sea
SUP3	DOUBLE SEA VIEW	str--AA--d--	Standard Double Room views Sea
SUP4	Double Sea View A	str--AA--d--	Standard Double Room views Sea
SUP5	Double Sea View	str--AA--d--	Standard Double Room views Sea
SUP6	double room,sea view	str--AA--d--	Standard Double Room views Sea
SUP7	Double Sea View BB	str--AA--d--	Standard Double Room views Sea
SUP8	Double Sea View HB	str--AA--d--	Standard Double Room views Sea
SUP9	Habitacion doble con vistas al mar 2A	str--AA--d--	Standard Double Room views Sea
SUP10	Main Building Double Seaview Room	str--AA--d--	Standard Double Room views Sea

Important characteristics

• Real-time generation: Occurs at Search time for every room in the response; there is no static room master list
• Not Seller-validated: Generated automatically; Sellers do not validate individual room outputs
• Source-dependent quality: Output depends on clarity and structure of the native description provided
• Attributes may be incomplete: If an attribute is not present or inferable from the native text, it may be missing from the standardized output
• Grouping signal, not guarantee: Rooms with the same standardized code may have minor commercial differences; review native values when exact equivalence matters

Room standardization

Room standardization is generated in real time from the Supplier-native room description and is not Seller-validated.

The standardized code and description are intended to facilitate comparison and aggregation. They do not guarantee that rooms with the same FastX output are commercially identical in every respect.

The Supplier-native room code and description are preserved in the Search response and should be reviewed whenever exact product equivalence is material.

Native room data

Supplier-native room codes and descriptions are always preserved in the response alongside FastX standardized values. Reference native codes and descriptions whenever exact product equivalence is material.

Use Cases

Supplier room list

Room list for specific room code

Use the Rooms List Query to filter specific room types. For example, if you want to focus on a Seller's double room inventory, include roomCodes such as "2269" in your criteria (in this example, it corresponds to the Seller's "Double Standard" room). This helps you retrieve more targeted and relevant results.