UCP Checker
Lodging · dev.ucp.lodging (on main)

UCP for Lodging

Lodging has a draft spec. The booking part of a hotel stay is drafted in the UCP spec. Here is what it covers, what is open, and how to try it on a test hotel.

Draft spec · not in a release Words last checked against the spec repo on 17 Nov 2026 · proposals synced daily, last 22 Nov 2026

Merged into the spec on 24 September 2026. Not in a release. The current release, 2026-08-25, has no lodging.

The draft is on the spec's main branch and marked as a draft that may change in ways that break, so names and fields may change.

Capability
dev.ucp.lodging.bookingThe booking session
Extension
dev.ucp.lodging.policy.cancellationCancellation terms on a booking
Merged
24 Sep 2026PR #780 · commit c9a1395
In a release
noneCurrent release: 2026-08-25

Timeline

  1. 24 Jun 2026 Charter filed (#543)
  2. 11 Aug 2026 Council announced (#714)
  3. 24 Sep 2026current spec Draft merged (#780)
  4. 15 Oct 2026 Eight proposals filed (#953–#960)
  5. 8 Dec 2026planned Release 2026-12-08 2 lodging changes · 0 merged
  6. 30 Mar 2027planned Release 2027-03-30 2 lodging changes · 0 merged
01What the draft covers

Booking a stay, in three steps

A UCP agent starts from a room and rate it already found, and ends with a confirmed reservation. The hotel or booking site sets the price, says what it needs to finish, and takes the payment.

  1. Open a booking session

    The agent sends the property and the stay it wants: room type, rate plan, dates and guests. The hotel answers with its own price and availability. From here the session is binding, not a search result.

    POST /booking-sessions
    create_booking_session
  2. Add guests and payment

    Over one or more updates: who books and pays, who stays, and when it's paid. Each update replaces the whole session. If the price moves, the hotel must say so and the agent must show it.

    PUT /booking-sessions/{id}
    update_booking_session
  3. Complete

    When everything is in place, the agent completes and gets a confirmation number. Without the AP2 mandates extension, the guest confirms in a screen they trust.

    POST /booking-sessions/{id}/complete
    complete_booking_session

Six statuses, set by the hotel

also: get_booking_session · cancel_booking_session
incomplete ready_for_complete complete_in_progress completed requires_escalationhand the guest over via continue_url canceledexpired or invalid, from any status

What a booking is made of

Every field in the draft's booking schema. "Required" is the schema's own list. It also carries the parts every UCP session shares: ucp, context, signals, messages and actions.

FieldSet byWhat it isRequired
propertyAgent sends, hotel confirmsThe hotel, resort or rental: a location and pictures.Required
stays[]Agent sends, hotel confirmsOne entry per unit booked, each with its own total for the whole stay.Required
accommodation_typeHotelThe room type, villa or pitch, with how many it sleeps.Required
rate_planHotelThe terms for that unit: flexible, non-refundable, member rate.Required
stay_datesAgentCheck-in to check-out.Required
occupancyAgentAdults, children and their ages; checked against what the room sleeps.Optional
guest_assignments[]AgentWho sleeps in this unit: primary or accompanying.Optional
bookerAgentThe person or company that books and pays. Kept apart from the guests. From ready_for_complete on, the session needs an identified lead: a booker with a name and contact, or a primary guest.Optional
guests[]AgentThe people staying. Their ids are made by the agent for this session only and carry no personal data. A primary guest with a name can be the identified lead.Optional
travel_purposeAgentbusiness or leisure; a hotel ignores values it doesn't know.Optional
totals[]HotelThe all-in price of the stay: subtotal, fees, taxes, discounts, and one total they add up to.Required
paymentAgentThe payment term chosen and, when needed, the card. Required to complete.On complete
policies[]HotelTerms such as cancellation (below).Optional
expires_atHotelHow long the session, its quoted price and any room hold last.Optional
continue_urlHotelWhere the guest finishes when the agent can't. Required when the status is requires_escalation.Optional
confirmationHotelThe reservation number once completed, with an optional PIN and link. Required when the status is completed.Optional
id · status · currency · linksHotelThe session's id and status, the currency the hotel picked, and legal links (privacy, terms).Required
  • propertyRequiredThe hotel, resort or rental: a location and pictures.
  • stays[]RequiredOne entry per unit booked, each with its own total for the whole stay.
  • bookerOptionalThe person or company that books and pays. Kept apart from the guests. From ready_for_complete on, the session needs an identified lead: a booker with a name and contact, or a primary guest.
  • guests[]OptionalThe people staying. Their ids are made by the agent for this session only and carry no personal data. A primary guest with a name can be the identified lead.
  • totals[]RequiredThe all-in price of the stay: subtotal, fees, taxes, discounts, and one total they add up to.
  • paymentOn completeThe payment term chosen and, when needed, the card. Required to complete.
  • policies[]OptionalTerms such as cancellation (below).
  • expires_atOptionalHow long the session, its quoted price and any room hold last.
All fields
  • stays[] · accommodation_typeRequiredThe room type, villa or pitch, with how many it sleeps.
  • stays[] · rate_planRequiredThe terms for that unit: flexible, non-refundable, member rate.
  • stays[] · stay_datesRequiredCheck-in to check-out.
  • stays[] · occupancyOptionalAdults, children and their ages; checked against what the room sleeps.
  • stays[] · guest_assignments[]OptionalWho sleeps in this unit: primary or accompanying.
  • travel_purposeOptionalbusiness or leisure; a hotel ignores values it doesn't know.
  • continue_urlOptionalWhere the guest finishes when the agent can't. Required when the status is requires_escalation.
  • confirmationOptionalThe reservation number once completed, with an optional PIN and link. Required when the status is completed.
  • id · status · currency · linksRequiredThe session's id and status, the currency the hotel picked, and legal links (privacy, terms).

Source: source/schemas/lodging/booking.json and types/*.json on main at c9a1395

dev.ucp.lodging.policy.cancellation

Cancellation, as data

Each cancellation policy carries one of three well-known labels, plus a written description that must not contradict it.

refundablepartially_refundablenon_refundable

Cutoff times and penalties are in the written description, not in fields.

dev.ucp.common.payment.terms

The price, and when it's paid

The total says what the stay costs. Payment schedules say when, and they must add up to that same total. Lodging's draft uses immediate, deferred and at_property.

immediatedeferredat_property

A resort fee paid at the hotel is part of the total; only its timing differs. The hotel must not complete at a different price without first returning new totals.

Not in the draft

  • Finding a hotelSearch and discovery come before a booking session and aren't covered.
  • After the bookingChanging, cancelling or checking in to a confirmed stay is left to separate post-purchase extensions.
  • Booking for someone elseNo fields beyond booker and guest for a travel agency booking on a guest's behalf, or for guests who aren't people.

Source: PR #780 "Out of Scope" and #858 non-goals

02What's next

What's next for lodging

Changes planned for the next releases, from the spec repo's milestones. A plan, not a promise: any of them can move or close.

Planned · 8 Dec 2026 2026-12-08 2 changes · 0 merged
Planned · 30 Mar 2027 2027-03-30 2 changes · 0 merged
No release 17 open, not planned for a release

Planned for 2026-12-08

2 changes
  • #1068
    Lodging non-Identify Loyalty Membership capture
    proposal
  • #1103
    Lodging booking session - expected total
    proposal

Planned for 2027-03-30

2 changes
  • #861
    The change itself
    Draft pull request for #807, rebuilt on main after the draft merged (it replaces #808).
    draft PR
  • #858
    Operation names
    Keep the _session suffix (create_booking_session) or match Retail's shorter names (create_checkout).
    proposal

Proposals, no release

open issues
  • #1065
    Non-200 responses documentation consistency
    proposal
  • #1066
    Lodging
    proposal
  • #991
    Corporate negotiated-rate entitlement for lodging
    proposal
  • #986
    Where a stay id comes from
    Whether a hotel can create a stay id on its own site, and sign its offer, before the booking session starts. Raised during #780 and set aside there as out of scope.
    proposal
  • #953
    Traveler identity fields
    Standard names for date of birth, nationality, country of residence and gender on guest and booker.
    proposal
  • #955
    Local currency at the property
    Show charges paid at the hotel in its own currency, beside the converted amount.
    proposal
All 17 open with no release on GitHub ›

Source: milestones, pull requests and issues labelled area:lodging, Universal-Commerce-Protocol/ucp, synced 22 Nov 2026

03Who's involved

Chartered under the Lodging Tech Council

The booking draft was proposed and merged in the spec repo (PR #780) under the council's charter. Anyone can file a proposal there.

Lodging Tech Council · announced 11 Aug 2026

Amadeus, Booking.com, Expedia, Google, Hilton, Marriott and Trip.com

Inaugural members, from the council's announcement (discussion #714). The 25 September announcement of the draft also credits open-source contributors (#864).

Charter · #543 · filed 24 Jun, closed 10 Aug 2026

It names Google surfaces as the first platform to use the capabilities, and Booking.com, Expedia, Hilton, Trip.com, Amadeus and Marriott as the first businesses. Its plan, in its own words:

Phase 1
Checkout: rate selection, availability, guest details, payment. The booking draft covers this.
Phase 1.5
Identity linking and loyalty.
Future
Hotel search, discounts and upsells. The charter gives no timing.
04Try it now

Book a test stay at Harbour Row

Our own test hotel speaks the draft. Point a UCP agent at it, or call it yourself. Test cards only; nobody is expecting you.

Test hotel · Staysstays.ucpsandbox.com

Harbour Row Stays

A small guesthouse on the harbour: four room types, with flexible, non-refundable and member rates, paid when you book or at the property.

Its UCP profile declares
  • dev.ucp.lodging.bookingdraft
  • dev.ucp.lodging.policy.cancellationdraft
  • dev.ucp.common.payment.terms2026-08-25
  • dev.ucp.common.location.lookup2026-08-25

REST at /ucp and MCP at /mcp. It also has three tools of its own that the draft doesn't define: search_properties, get_booking and cancel_booking. cancel_booking cancels a confirmed test booking; the draft itself has no way to do that.

Example · simplifiedopen a booking session
POST https://stays.ucpsandbox.com/ucp/booking-sessions
{
  "property": { "id": "[PROPERTY ID]" },
  "stays": [{
    "id": "[STAY ID from search]",
    "stay_dates": { "start_date": "2026-10-30",
                    "end_date":   "2026-11-01" },
    "occupancy":  { "adults": 2, "total": 2 }
  }]
}

→ the hotel answers with
{
  "status": "incomplete",
  "totals": [ … one all-in total … ],
  "policies": [{
    "type": "dev.ucp.lodging.policy.cancellation",
    "refundability": "refundable"
  }],
  "expires_at": "[when the quoted price lapses]"
}

Field names from the draft schema; values are placeholders.

Rules in the draft a test run exercises

  • MUSTOne all-in totalTaxes and fees paid at the hotel are in it, and the payment schedules add up to it.
  • MUST NOTNo silent price changeThe hotel returns new totals, with a warning the agent shows, before completing at a different price.
  • MUST NOTNo personal data in guest idsGuest ids are made by the agent for one session and never used to link sessions.

Source: docs/specification/lodging/booking/index.md at c9a1395

05FAQ

Common questions

Is there a UCP spec for booking hotels?

A draft. dev.ucp.lodging.booking and its cancellation extension were merged into the spec repo on 24 September 2026 (PR #780). It covers the booking session, from a chosen room and rate to a confirmed reservation.

Is it in a release?

Not in a release. The current release, 2026-08-25, has no lodging. The booking capability (#780) has no release milestone of its own, so the spec repo doesn't say which release it will join, and its documentation marks it as a draft. Changes to it, such as the open design questions (#858) and set schedules for cancellation policies (#861), are planned on the repo's milestones, a plan that can move; What's next on this page lists each one with the release it is planned for.

Should a hotel build on it?

The spec marks it as a draft that may change in ways that break. Building against it means following one commit, c9a1395, and expecting names to move; #858 already questions the operation names.

Does it cover finding a hotel?

No. Search and discovery are out of scope. A booking session starts from a property, room type and rate the agent already has.

All questions

Can an agent cancel a confirmed reservation?

Not with this draft. cancel_booking_session ends an unfinished session. Changing or cancelling a confirmed stay is left to separate post-purchase extensions, which the spec does not define. Our test hotel has its own cancel_booking tool for testing; it isn't part of the draft.

How do deposits and pay-at-hotel work?

The total is the full price of the stay. Payment terms split when it's paid (immediate, deferred, at_property), and every schedule in a term must add up to the total. A pay-at-property booking completes with an empty payment when no card guarantee is needed.

Every fact on this page: Universal-Commerce-Protocol/ucp and our test hotel, read 17 Nov 2026.

Sources
From our blog