Clients use our end-points to create different types of bookings, including:
- Single room reservations
- Homogeneous multiple-room reservations
- Heterogeneous multiple room reservations (rooms with different Room Types, RatePlans, Check-In and Check-Out dates)
Each booking has a unique HT Confirmation Code.
ClientOtaCode - If a booking exists with the same clientOtaCode, we reject the booking with the error “Duplicate Request”. See more details in the section below.
Hote Trader Confirmation Code Structure
For all regular bookings: HT-XYXYXY - where any digit can be a number, 0 and 1 excluded. All associated rooms will have HT-XYXYXY-1, -2 so on.
For all rooms in the same service, clientOtaCode will be the same, HT Code will be different.
Example 1
For 1 service and 2 room bookings, HT-ABCDEF is the HT Code for reservation.
Room will have HT-ABCDEF-1 (1st room in the service, clientOtaCode = TestClient-Book-test)
Room will have HT-ABCDEF-2 (2nd room in the service, clientOtaCode = TestClient-Book-test)
Example 2
For 2 services, 2 rooms in each service booking, HT-ABCDEF is the HT Code for reservation.
Room will have HT-ABCDEF-1 (1st room in 1st service, clientOtaCode = TestClient-Book-test-1)
Room will have HT-ABCDEF-2 (2nd room in 1st service, clientOtaCode = TestClient-Book-test-2)
Room will have HT-ABCDEF-3 (1st room in 2nd service, clientOtaCode = TestClient-Book-test-2)
Room will have HT-ABCDEF-4 (2nd room in 2nd service, clientOtaCode = TestClient-Book-test-2)
Example 3
Booking for 1st Property, 2 rooms: HT-ABCDEF, propId = 277
Room1: HT-ABCDEF-1, clientOtaCode = TestClient-book-test
Room2: HT-ABCDEF-2, clientOtaCode = TestClient-book-test
Booking for 2nd Property, 1 room: HT-ABCDEF-P1, propId = 281
Room1: HT-ABCDEF-P1-1, clientOtaCode = TestClient-book-test
Booking for 3rd Property, 2 rooms: HT-ABCDEF-P2, propId = 290
Room1: HT-ABCDEF-P2-1, clientOtaCode = TestClient-book-test
Room2: HT-ABCDEF-P2-2, clientOtaCode = TestClient-book-test