Migrating Bathroom facility use cases
This topic outlines the different use cases that you can implement when using the bathroom facilities endpoints.
- Migrating a home type bathroom facility
- Migrating a hostel type bathroom facility
- Migrating a hotel type bathroom facility
Use case 1: Creating a bathroom for a home group
Consider the following bathroom facility setup as defined in the extranet for a home property type.
Using the OTA_HotelDescriptiveContentNotif endpoint
When using the OTA_HotelDescriptiveContentNotif endpoint you can pass the following payload:
Migrating to the bathroom facilities endpoint
When migrating to the facilities-api/properties/{propertyId}/rooms/{roomId}/bathrooms endpoint, you can pass the following payload:
{
"property_bathroom_details": {
"bathrooms": [
{
"bathroom_type": "PRIVATE",
"bathroom_location": "NEXT_DOOR"
},
{
"bathroom_type": "SHARED",
"bathroom_location": "OPPOSITE_THE_ROOM"
}
]
}
}Use case 2: Creating a bathroom for a hostel
Consider the following bathroom facility setup as defined in the extranet for a hostel property type.
Using the OTA_HotelDescriptiveContentNotif endpoint
This set up was not supported using the OTA_HotelDescriptiveContentNotif endpoint
Migrating to the bathroom facilities endpoint
When migrating to the facilities-api/properties/{propertyId}/rooms/{roomId}/bathrooms endpoint, you can pass the following payload:
{
"property_bathroom_details": {
"bathrooms": [
{
"bathroom_type": "PRIVATE",
"bathroom_location": "NEXT_DOOR",
"hostel_bathroom_details": {
"bathroom_facilities": [
{
"type": "SHOWER",
"count": 2
},
{
"type": "TOILET",
"count": 1
},
{
"type": "TOILET_PAPER"
},
{
"type": "HAIR_DRYER"
},
{
"type": "SLIPPERS",
"is_paid": true
},
{
"type": "BIDET"
},
{
"type": "TOOTHBRUSH",
"is_paid": true
},
{
"type": "SHAMPOO",
"is_paid": false
},
{
"type": "CONDITIONER",
"is_paid": false
},
{
"type": "BODY_SOAP",
"is_paid": true
},
{
"type": "TOWEL",
"is_paid": false
},
{
"type": "HOT_WATER"
}
]
}
}
]
}
}
Use case 3: Creating a bathroom for a hotel
Consider the following bathroom facility setup as defined in the extranet for a hotel property type.
Using the OTA_HotelDescriptiveContentNotif endpoint
When using the OTA_HotelDescriptiveContentNotif endpoint you can pass the following payload:
Migrating to the bathroom facilities endpoint
When migrating to the facilities-api/properties/{propertyId}/rooms/{roomId}/bathrooms endpoint, you can pass the following payload:
{
"hotel_bathroom_details": {
"private_bathroom_state": "PRESENT",
"shared_bathroom_state": "MISSING",
"private_bathroom_details": {
"type": "EXTERNAL_BATHROOM",
"location_type": "OTHER",
"location_other": "outside of the room"
},
"number_of_bathrooms": 2
}
}