Book with your price
When you have a contracted price with the hotel and your system already knows what a room costs, book it at that price directly. There is no search and no thirty-minute window.
This works only on rate plans with booking_types.fit (see
Content). Whether a rate plan allows it is the hotel's
decision, agreed with you.
POST /booking/with-price
{
"property": 1860,
"ref_id": "AG-2026-00418",
"checkin_date": "2026-07-14",
"checkout_date": "2026-07-21",
"client": {
"first_name": "Ivan",
"last_name": "Petrov",
"email": "[email protected]",
"phone": "+359888123456"
},
"items": [
{
"ref_id": "AG-2026-00418-1",
"room": 5696,
"rate": 11058,
"occupancy": { "adults": 2, "children": [7] },
"price": 1240.00,
"currency": "EUR",
"guests": [
{ "first_name": "Ivan", "last_name": "Petrov", "adult": true },
{ "first_name": "Maria", "last_name": "Petrova", "adult": true },
{ "first_name": "Nikola", "last_name": "Petrov", "adult": false, "non_adult_age": 7 }
]
}
]
}
It takes the same fields as POST /booking, with these
differences:
- No
search_id, and noaccommodation_id. occupancyon each item:adults, andchildrenas a list of ages. The party has to be one the room can take.priceandcurrencyon each item: the price of that room for the stay.currencymust be the property'scurrency, unless the hotel lets you book that rate plan in another currency. Every item of a booking must use the same one (error 15 otherwise).guestsis required on each item, and must fitoccupancy: one adult per adult, and each child with an age fromoccupancy.children. Fewer names are filled in; one guest more, or a child of an age the occupancy does not have, is refused with error 6 "Occupancy not equal to guests!".extra_services: each extra is booked once;qtyis not used.client:first_name,last_name,email,phoneandnationalityare stored.company,i_want_invoiceandbooking_for_someone_elseare accepted but not stored today, nor arebeds_preferencesandbooking_timestamp.ref_id: as onPOST /booking, aref_idthat already names a live booking of yours is refused with error 13 (see Retrying safely).
What is checked
Your price is booked as it is, even for dates the hotel has not priced in
Quendoo. The stay itself is checked like a search booking. An item that
fails a check is refused with error 10 and a message that says why (see
Errors):
- The room is available for the dates. Closed dates are refused.
Availability is not checked for a booking request (
request-with-price), nor on a rate plan the hotel has set to accept your bookings without the availability check. Such a room takes no unit from the hotel's availability; every other check below still applies. - The rate plan can be booked today and is active for every night of the stay.
- The party fits the room's beds. The children's ages must fall in the hotel's age groups and in the room's own age range.
- The rate plan has an accommodation for exactly this party. The hotel has not switched it off, or disabled this combination of guests.
- The stay restrictions are met: minimum and maximum stay, closed to arrival or departure, advance booking.
The hotel can relax two of these for your agency, when your contract covers it:
- Stay restrictions: the rate plan's minimum and maximum stay, closed to arrival or departure and advance-booking rules are not checked. Closed dates still are.
- Any guests the beds can hold: the room's age range and the rate plan's accommodations are no longer checked. The beds, the hotel's age groups and whatever the hotel switched off still are.
Ask the hotel if you need either.
Letting the hotel's rules pick the rate plan
rate is optional. Leave it out and send what your system knows about the
sale instead. The hotel's selection rules then pick the rate plan:
| Field | |
|---|---|
market_country_code |
The market, as a two-letter country code |
meal_plan_code |
BO, BB, HB, FB, AI or UAI |
special_offer |
Your code for the offer |
subagent_1, subagent_2 |
Your sub-agents, if you sell through them |
The hotel sets these rules up in Quendoo for your agency. Agree with the hotel which values you will send before you rely on them.
The plan a rule picks is checked like one you name: you must hold it, it
must allow booking with a price, and the room must be able to take the
party. If no rule matches, the item is refused with error 8 and
nothing is booked. Send rate yourself, or ask the hotel for a rule that
covers the sale.
POST /booking/request-with-price
The same request, but it asks rather than books:
- the booking is created as
REQUESTED, not as a reservation; - the hotel confirms it (
APPROVED) or turns it down (CANCELLED); - subscribe to the
bookingwebhook to hear which, as soon as the hotel decides.
Use it when your contract with the hotel says your bookings need its
confirmation. The rate plan must allow booking requests for your agency;
otherwise the call is refused with error 6 ("Can't send booking request!").
POST /booking/with-price also creates a REQUESTED booking when the
property confirms every booking itself (booking_type: request).
Which booking call to use
| You have | Use |
|---|---|
| A client looking at offers right now | POST /search, then POST /booking |
| A room, a party and your contracted price | POST /booking/with-price |
| The same, but the hotel must confirm | POST /booking/request-with-price |
| A room and a party, and you want the hotel's live price | POST /booking/auto-price |