Facilities API
/
About Try it
/
Response

Facilities API (1.0)

Manage facilities at both the property- and room-level.\n Booking.com supports adding or assigning a variety of different facilities at the property- or room-level. Specify the facility ID along with any required parameters to assign a facility.\n\nFacilities are of the following types:

  • Single-instance facilities: You can assign these facilities only once to a property or a room. An example of a single-instance facility is: room service. There are two types of single-instance facilities:
    • Single-instance facilities that can be toggled on or off.
    • Single-instance facilities supporting optional parameters: Allows you to specify more details about the facility
  • Multi-instance facilities: You can assign multiple facilities of this type to a property. When adding multi-instance facilities you must provide additional details to add to a property or a room. Examples of multi-instance facilities are: Restaurant, Swimming pool and Parking.
Download OpenAPI description
facilities-api-specification.json
facilities-api-specification.yaml
Overview
URL https://connect.booking.com
Connectivity Team connectivity@booking.com
Languages
Servers
Test static response
https://developers.booking.com/_mock/connectivity/docs/openapispecs/facilities-api/facilities-api-specification/
Test using live endpoint
https://supply-xml.booking.com/facilities-api/

Manage property facilities

Use the GET and the PUT endpoints to:

  • Retrieve property-level facilities details
  • Add, modify or delete property-level facilities details
    • Add single-instance facilities
    • Add multi-instance facilities
Operations

Manage room facilities

Use the GET and the PUT endpoints to:

  • Retrieve room facilities set for a property.
  • Add, modify or delete room facilities.
Operations

Manage bathrooms

Use the GET and the PUT endpoints to:

  • Retrieve room bathroom configuration
  • Add, modify or delete room-level bathroom information
Operations

Meta data endpoint

Retrieve the latest facility definitions.

  • Get the list of all supported facilities
    • To get the details of a property-level facility: Look for a matching name under the facility_name in the response. To add this facility, you must specify the facility_id. Property-level facilities are listed under the property_facility_metas in the meta endpoint response.
    • To get the details of the room-level facility: Look for a matching name under the room_facility_name in the response. To add the facility, you must specify the room_facility_id. Room-level facilities are listed under the room_facility_metas in the meta endpoint response.
  • Details of the facilities such as ID, OTA code and any optional parameters.
Operations

About Try it

Learn how to effectively use the Try it feature in the Facilities API documentation.

Use the Try it feature to send test request examples to the API endpoints directly from the developer portal and depending on the selected environment either see static, pre-built responses or dynamic responses from a test property.

Request

Using the UI, toggle between Edit and Preview tabs to see the values applied to the path or query placeholders (if there are any). You can also click on any unresolved placeholders to add a value or edit an existing placeholder value.

The portal loads the default request body. Where the specification supports multiple request body examples (for example: Rooms API POST endpoint), you can choose a different request body from the drop-down list.

Some helpful pointers before running a request:

  • Authentication (when using live endpoint): Configure your authentication headers

    • API Key or OAuth token as required. Use the Environments tab.
    • Make sure to manage separate machine accounts for test vs. properties in production.
    • Ensure credentials match your selected environment.

  • Parameters: Fill in required parameters

    • Path parameters (like propertyId)
    • Query parameters (like language_code)
    • Request body for POST/PUT operations

  • Execute: Click Send to send the request

    • The request is sent to the selected environment
    • When sending requests to the live endpoint, real HTTP request is made to the API

Response

The Try it feature provides comprehensive response information to the extent supported by the Open API specification:

Status code

  • 2xx: Success responses (200)
  • 4xx: Client errors (400 Bad Request, 401 Unauthorized, 404 Not Found)
  • 5xx: Server errors (500 Internal Server Error)