Developers » Build your own booking engine
Build your own booking engine
Design your own booking pages and let Quendoo do the rest: prices, availability, policies, the booking and the payment. You see exactly what the property's own booking engine shows.
- Pick the booking module. A property sells through one or more booking
modules, each with its own rates and settings:
GET /v1/qc/properties/{id}/booking_buttons. - Search.
GET /v1/qc/properties/{id}/booking_offers?format=enginewithbooking_button_id,checkin,checkoutandrooms. One answer holds everything for the page:content: the property, rooms with photos, amenities and bed layout, rate plans, payment methods, terms and special offers;results: every room and rate with its price, availability, nightly prices, cancellation and payment policy, meal plan, discounts and extras, and thepayment_planit would be booked with (amounts and due dates), ready to show next to the price.
- Pass your visitor as
guest_ipandguest_user_agent. Country-targeted rates and mobile promotions then apply exactly as on the property's own booking engine. - Show the summary.
POST /v1/qc/properties/{id}/bookings/previewwith thesearch_tokenand the chosenoffer_ids and extras: every line, the total and the payment plan of the whole booking, exactly as it will be written. Nothing is booked yet, preview as often as the cart changes. - Book.
POST /v1/qc/properties/{id}/bookings/from-searchwith thesearch_token, theoffer_idof each chosen room, the guest and, if you like, your ownpartner_reference. The price is the one you showed, as long as you book beforeexpires_at(30 minutes). A token books once. - Take the guest to pay. The answer carries
payment_url, the hotel's payment page for the first instalment, and the wholepayment_plan. If an instalment stays unpaid pastauto_cancel_after, the booking is cancelled.
Several hotels. With a token for several hotels, GET /v1/qc/booking_offers searches them all at once (each through the module its
hotelier chose, each with its own search_token), and POST /v1/qc/bookings/batch books one guest at several of them, all or none —
with bookings/batch/preview as its summary step.
Bookings you make arrive on the bookings feed like any
other, under the source code QCN.
Details: API reference.