Contains Rooms API specification
Rooms API (1.2)
Download OpenAPI description
Overview
URL
Connectivity Team
Languages
Servers
Test static response
https://developers.booking.com/_mock/connectivity/docs/openapispecs/rooms-api/rooms-api-specification
Test using live endpoint
https://supply-xml.booking.com
Request
Retrieve meta data required for unit creation and update for any supported language_code
- Retrieve the list of all unit type IDs allowed for creation/update. For each
$.unit_types[*]record you will find: unit_type_id: the unit type ID you must provide with each create and update requestunit_type_name: string representation of unit type ID (translatable)is_multi_room: attribute that defines what type of room types you can use add in your unitis_active: attribute that defines if a unit type is available for creation/update, inactive room types are available for read onlyvalid_property_categories: list of property categories that allow creation of this unit typesuggested_unit_names: list of unit names that we recommend to use in combination with this unit type- Retrieve the list of all room name IDs allowed during unit creation/update. For each
$.unit_names[*]record you will find: unit_name_id: the unit name ID you must provide with each create requestunit_name: string representation of unit name ID (translatable)- Retrieve the list of all bed type IDs allowed during unit creation/update. For each
$.bed_types[*]record you will find: bed_type_id: the bed type ID you must provide when configuring roomsbed_type_name: string representation of bed type (translatable)bed_type_description: description of bed type size using metric units (translatable)bed_type_description_imperial: description of bed type size using imperial units (translatable)is_active: attribute that defines if a bed type is available for creation/update, inactive bed types are available for read only- Retrieve the list of all property categories for which you can create a unit. For each property type you will find its name and category ID, as well as an OTA or a Booking.com extended code
- Test static responsehttps://developers.booking.com/_mock/connectivity/docs/openapispecs/rooms-api/rooms-api-specification/rooms-api/meta
- Test using live endpointhttps://supply-xml.booking.com/rooms-api/meta
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://developers.booking.com/_mock/connectivity/docs/openapispecs/rooms-api/rooms-api-specification/rooms-api/meta?language_code=EN_GB&show_inactive=true'Response
application/json
{ "data": { "language_code": "EN_GB", "unit_types": [ … ], "unit_names": [ … ], "bed_types": [ … ], "property_categories": [ … ] }, "warnings": [ { … } ], "errors": [ { … } ], "meta": { "ruid": "string" } }
About Try it
Learn how to effectively use the Try it feature in the Rooms 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.