Rooms And Rates

🛏️ Rooms and Rates API

The Rooms and Rates API provides detailed information about hotel rooms and their pricing to help users find the best available options.

The API organizes room and rate data into multiple options, where each option represents a bookable set of rooms. Each rate option includes comprehensive details such as:

➡️ It’s important to proceed with a specific option for booking, as only the rate and rooms from that chosen option will be booked.

🔑 Key Identifier

Each rate option includes a unique ID called recommendationId, which is required for booking.

📦 Key Components of API Response

• Rooms – Contains room name, description, facilities, bed configuration, and size.
• Options – Each represents a specific rate. Includes recommendationId.
  • Board Basis - Standardized meal-plan info for each rate (e.g. Room Only, Bed & Breakfast, Half Board).
• Standardized Rooms – Ensures data consistency by normalizing room details across suppliers.

This API enables seamless integration and provides structured, accurate hotel room pricing information.

Usage: Call Rooms and Rates with the hotelId and traceId from Search. Show the standardized rooms, list the options under each, and let the customer choose one. Send the chosen optionId and the roomIds to /pricecheck and then to /book. Check the passport, PAN and guest info flags before collecting guest details, so the booking form asks for everything the supplier needs.

📘 API Reference: Rooms and Rates API Documentation

🥘 Board Basis (Field Deep Dive)

Each rate returned in the Rooms and Rates response carries its own boardBasis, since different rates for the same room can have different meal plans (e.g. Room Only vs Bed & Breakfast vs Half Board for the same standardized room).

Field in API Response

boardBasis is an object present on every rate - results.options[].rate.boardBasis.

Example:

"boardBasis": {
  "description": "Room only",
  "type": "RoomOnly"
}

boardBasis.type – Unique Types List

This is a closed/fixed list — every rate's boardBasis.type must be one of these 5 values.

Usage – Filters & Standardization of Board Basis

Filters: System filter/sort results by meal plan using boardBasis.type (e.g. "Only Bed & Breakfast options" or "Only Room Only"). Filtering must never be done on boardBasis.description — only on boardBasis.type.
Standardization logic: Volt maps each raw meal-plan string to one of the 5 fixed type values. Examples of raw strings mapped to the same standardized type:
→ RoomOnly: "Room Only", "ROOM ONLY", "room only", "Accomodation only", "Accommodation Only"
→ BedAndBreakfast: "Free breakfast", "Breakfast buffet", "BED AND BREAKFAST", "Bed & Breakfast", "Continental breakfast", "Breakfast Included", "room with breakfast"
→ HalfBoard: "Half board", "HALF BOARD", "breakfast and dinner"
→ FullBoard: "Full board", "FULL BOARD"
→ AllInclusive: "All Inclusive", "All-inclusive", "All Included"

boardBasis.description -

The description field is closer to the raw text and is not guaranteed to be a clean meal-plan phrase — it can carry extra context that has no bearing on type. Below are real patterns grouped by the categories flagged for review:

Usage – What to show end users
boardBasis.type is what should drive filters, badges/icons, and any comparison logic (e.g. sort by meal plan, "Free Breakfast" badge).
boardBasis.description can be shown as supplementary text under the rate (e.g. small print), since it may contain useful context (pax limits, discounts, exact hotel wording) that type doesn't capture