Property API implementation use cases

This topic discusses all the possible scenarios supported by the Property API.

Scenario 1 - Publish a property to Booking.com for the first time

Use the POST property-api endpoint to create a property. Make sure to specify the legal entity ID (LEID) along with the minimum requirements. For more information, see Creating property details.

You may encounter an error while creating a property when your request:

• Does not specify all the required parameters or includes extra parameters.
• Tries to create a property that already exists on Booking.com. For example, property details cannot match existing property name, address line 1 and latitude/longitude values. The response includes the Booking property ID whose LEID of the partner matches.

Scenario 2 - Import an existing property from Booking.com into your system

Use the GET property-api endpoint and specify the property ID to retrieve the property details.

Points to note:

• You must have permission to access the property.
• You can access the property information in pending connection status.

For more information, see Retrieving property details.

Scenario 3 - Check for changes made on Extranet or sync property against current values on Booking.com

Use the GET property-api endpoint and specify the property ID to retrieve the property details. For more information, see Retrieving property details.

Scenario 4 - Add additional information such as star rating, number of floors and currency code

Use the PATCH property-api endpoint and specify the property ID along with all the information to add or change. For more information, see updating property details.

For additional assistance, contact the Booking.com Connectivity Support team.

Quick Actions

→ To create and manage property details, see Managing property details.
→ To troubleshoot Property API errors, see Troubleshooting Property API error responses.