Quendoo DEVELOPERS API documentation →
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.

  1. 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.
  2. Search. GET /v1/qc/properties/{id}/booking_offers?format=engine with booking_button_id, checkin, checkout and rooms. 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 the payment_plan it would be booked with (amounts and due dates), ready to show next to the price.
  3. Pass your visitor as guest_ip and guest_user_agent. Country-targeted rates and mobile promotions then apply exactly as on the property's own booking engine.
  4. Show the summary. POST /v1/qc/properties/{id}/bookings/preview with the search_token and the chosen offer_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.
  5. Book. POST /v1/qc/properties/{id}/bookings/from-search with the search_token, the offer_id of each chosen room, the guest and, if you like, your own partner_reference. The price is the one you showed, as long as you book before expires_at (30 minutes). A token books once.
  6. Take the guest to pay. The answer carries payment_url, the hotel's payment page for the first instalment, and the whole payment_plan. If an instalment stays unpaid past auto_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.