Quendoo DEVELOPERS API documentation →
Developers » Content

Content: locations, amenities and properties

Three read-only calls give you everything you need to show a hotel in your own system: where it is, what it offers, and which rooms and rate plans you may sell. Content changes rarely, so load it once, store it, and refresh it daily rather than on every client request.

Every call needs Authorization: Bearer {token}. Base URL: https://b2b.quendoo.com/api/b2b/v1.

Languages

You choose the language of translated texts with locale, a two-letter code: en, bg, el, de, ro, ru or pl. Any other value is refused with error 2. Store what you receive per locale.

GET /locations

Every location (city, resort) on the platform that has a name in the language you ask for, whether or not you sell a property there.

Parameter Required
locale yes Language of the names

Each id comes as a numeric string ("37"). Send it as an integer in locations of POST /search, and match it to the integer location_id on each property (0 means the property has no location).

GET /amenities

The list of property-level amenities: air conditioning, Wi-Fi, distance to the airport and so on. The list is the same for every hotel. A hotel picks from it and cannot add its own. Room amenities are not in this list: they come with each room in /properties, already named.

For an amenity that takes one or more of a fixed set of values, options is the list of those values as text in your locale.

Parameter Required
locale yes Language of the names

An amenity is something that is always true of the property or the room. Something included or sold per rate plan (breakfast, a transfer, parking) is an extra service instead, and comes with the property.

GET /properties

Every property you can sell, with its rooms and the rate plans the hotel has shared with you.

Parameter Required
locale yes Language of the texts
properties no Comma-separated property ids, to fetch only these

Each property carries:

Field Meaning
booking_types.search The plan can be booked from a search (POST /booking) or at our price (auto-price)
booking_types.fit The plan can be booked at your own price (POST /booking/with-price)
agency_info commission_type: net (you see net prices), or commission with commission_percent
sell_type per_room, per_person or per_occupancy: how the price is built
meal_plan_code BO, BB, HB, FB, AI or UAI
payment_policy When payment is due, and how much
cancellation_policy What a cancellation costs, and when
extra_services_included Extras already in the price
extra_services_available Extras sold on top, which you can book with the room

The older per_room flag is still sent for existing integrations. Use sell_type instead.

Keeping it fresh