Quendoo DEVELOPERS API documentation →
Developers » Search and book

Search and book

The standard way to sell: search for a stay and a party, show your client the offers, and book the one they choose. The search prices everything with the hotel's own engine, the same one behind the hotel's website, so the price you book is exactly the price you showed.

POST /search

{
  "locale": "en",
  "checkin_date": "2026-07-14",
  "checkout_date": "2026-07-21",
  "occupancy": [
    { "adults": 2, "children": [7, 4] },
    { "adults": 2 }
  ],
  "properties": [1860]
}
Field Required
locale yes Language of the texts
checkin_date, checkout_date yes YYYY-MM-DD
occupancy yes One entry per room: adults, and children as a list of ages
locations, properties, country_codes no Narrow the search

The answer has three parts:

Only rate plans with booking_types.search are returned, because only those can be booked this way.

POST /booking

{
  "search_id": "…",
  "property": 1860,
  "ref_id": "AG-2026-00417",
  "checkin_date": "2026-07-14",
  "checkout_date": "2026-07-21",
  "client": {
    "first_name": "Ivan",
    "last_name": "Petrov",
    "email": "[email protected]",
    "phone": "+359888123456"
  },
  "notes": "Late arrival",
  "items": [
    {
      "ref_id": "AG-2026-00417-1",
      "room": 5696,
      "rate": 11058,
      "accommodation_id": "…",
      "extra_services": [ { "id": 412, "qty": 1 } ],
      "guests": [
        { "first_name": "Ivan", "last_name": "Petrov", "adult": true },
        { "first_name": "Nikola", "last_name": "Petrov", "adult": false, "non_adult_age": 7 }
      ]
    }
  ]
}
Field Required
search_id yes From the search, within its thirty minutes
property yes One booking is for one property
checkin_date, checkout_date yes The dates you searched for
client yes first_name, last_name, email, phone; optionally nationality, i_want_invoice, booking_for_someone_else, and company (name, address, reg_no, vat_no, rp_name) for an invoice
items yes One per room: room, rate and accommodation_id
items[].extra_services no Extras that were in the offer you searched, as id and qty (at least 1)
items[].beds_preferences no Accepted, but not stored today
items[].guests no Names, and the age of each child (non_adult_age)
ref_id, items[].ref_id no Your own ids for the booking and for each room
booking_timestamp no Accepted, but not stored today: the booking's booking_dt_unix is when we created it

A field that is not in this table is refused with error 4.

The answer is the booking, in the shape GET /booking returns. This call takes no locale, so its texts (hotel, room and policy names) come in the hotel's own language; read the booking with GET /booking?locale=… for yours. Its booking_status tells you where it stands:

A booking that waits for the hotel (REQUESTED, then APPROVED or CANCELLED, with a webhook for each) is made through request-with-price or request-auto-price, or through with-price and auto-price on a property that confirms bookings itself (booking_type: request).

Rules worth knowing

Need the price of one stay without showing a list first? See Book at our price. Selling at a price you contracted with the hotel? See Book with your price.