MyHotelWorks

Module 02 — Central Reservations

The website and the front desk, quoting the same number.

Most hotels run a booking engine that keeps its own copy of rates and availability, then spend the rest of the year reconciling it. Ours has no copy. Your website calls the same pricing engine the front desk uses, so there is nothing to drift.

Where this module stands

The booking API is built and documented. The administration screens are not — channel setup is configuration today, and there is no CRS console yet. We would rather tell you that now than during implementation.

Talk to us about integrating

One engine, three faces

Your website
Call centre
OTA partner
↓↓↓
Public booking API4 versioned routes · channel header
↓
Shared availability & pricing enginethe same code the front desk runs
↓
One reservation record
One inventory count

No nightly sync, no second database, no "the site said 180 but the system says 210."

Four routes, deliberately.

A narrow public contract, versioned separately from the internal reservation API — so we can refactor inside without breaking your integration.

RouteWhat it does
GET/v1/shop Returns bookable room type and rate combinations for a stay, cheapest first, with live counts. Only what can genuinely be sold — inactive rates, internal-only rates, rates outside their sell window and unpriced rates never appear.
POST/v1/booking Creates a real reservation in the property's system and returns a guest-facing confirmation number. Safe to retry: the same idempotency key returns the original booking rather than making a second one.
GET/v1/booking A guest looks up their booking with the code they were given, scoped to one property so a code cannot be used to walk the estate.
POST/v1/cancel Self-service cancellation when no cancellation charge applies. When money is owed, it refuses and directs the guest to the property — a CRS process cannot post to a folio, and we would rather it say so than guess.

Guarantees worth reading the small print for.

Most of what goes wrong with booking integrations goes wrong in three places. These are handled at the engine, not by asking your developers to be careful.

The client cannot send a price

A booking request carries no amount. The server re-quotes from the same procedures the search used, so a stale page or a tampered request cannot become a booked rate.

A retry cannot double-book

The idempotency key is claimed in the database before any work begins, not checked and then written. Two simultaneous retries of the same request cannot both create a reservation.

A rate cannot be booked unseen

Before booking, the rate is re-checked against what that caller is allowed to see. Shopping a public rate and then booking a negotiated one by its ID does not work.

Negotiated rates stay private

Corporate rates unlock with an access code. A wrong code and a missing code return the same answer, so the endpoint cannot be used to discover which codes exist.

Confirmation numbers are safe to read aloud

Ten characters, no letters that sound alike over a phone, random rather than sequential — so codes cannot be guessed and your booking volume is not public.

Every booking carries its source

The channel header stamps market and source codes onto the reservation at creation, which is how revenue reporting separates the website from the call centre from an OTA.

Built, and not yet built.

Buying software on a roadmap is a decision you should make with the roadmap in front of you.

Available now

  • Availability search with public-rate filtering
  • Booking creation with server-side re-quoting
  • Booking retrieval by confirmation number
  • Penalty-free self-service cancellation
  • Access-code gating for negotiated rates
  • Channel attribution to market and source codes
  • Restrictions honoured in availability — closed, closed to arrival and departure, minimum and maximum stay
  • Allotments with elastic group overflow

On the roadmap

  • API authentication and rate limiting
  • Booking modification through the public API
  • Search across several properties in one call
  • Deposits and guarantees taken at booking
  • A CRS administration console
  • Per-channel rate loading and pricing
  • Outbound distribution to OTA channel managers
  • Competitor rate shopping

Today the API belongs on a private network or behind your own gateway. If internet-facing deployment is on your critical path, that is a conversation to have before you sign anything, not after.

Who this is for today.

The CRS suits teams who want to own their booking front end and integrate against a solid contract.

Hotels building their own booking site

You want the design and the guest journey under your control, and a rate and availability source you do not have to reconcile.

Call centre and reservations teams

Agents quoting from the same engine as the property, with every booking attributed back to the call centre for reporting.

Groups planning ahead

Properties already clustered for multi-property operation, adopting the PMS now and the distribution layer as it lands.

Read the contract before you commit.

We will send you the full API specification — routes, rules, failure modes and the security work still outstanding — so your developers can judge it rather than take our word for it.