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.
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. The booking sessionlodging. booking - Extension
- dev.
ucp. Cancellation terms on a bookinglodging. policy. cancellation - Merged
- 24 Sep 2026PR #780 · commit
c9a1395 - In a release
- noneCurrent release: 2026-08-25
Timeline
- 24 Jun 2026 Charter filed (#543)
- 11 Aug 2026 Council announced (#714)
- 24 Sep 2026current spec Draft merged (#780)
- 15 Oct 2026 Eight proposals filed (#953–#960)
- 8 Dec 2026planned Release 2026-12-08 2 lodging changes · 0 merged
- 30 Mar 2027planned Release 2027-03-30 2 lodging changes · 0 merged
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.
-
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 -
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 -
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
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.
| Field | Set by | What it is | Required |
|---|---|---|---|
| property | Agent sends, hotel confirms | The hotel, resort or rental: a location and pictures. | Required |
| stays[] | Agent sends, hotel confirms | One entry per unit booked, each with its own total for the whole stay. | Required |
| accommodation_type | Hotel | The room type, villa or pitch, with how many it sleeps. | Required |
| rate_plan | Hotel | The terms for that unit: flexible, non-refundable, member rate. | Required |
| stay_dates | Agent | Check-in to check-out. | Required |
| occupancy | Agent | Adults, children and their ages; checked against what the room sleeps. | Optional |
| guest_assignments[] | Agent | Who sleeps in this unit: primary or accompanying. | Optional |
| booker | Agent | The 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[] | Agent | The 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_purpose | Agent | business or leisure; a hotel ignores values it doesn't know. | Optional |
| totals[] | Hotel | The all-in price of the stay: subtotal, fees, taxes, discounts, and one total they add up to. | Required |
| payment | Agent | The payment term chosen and, when needed, the card. Required to complete. | On complete |
| policies[] | Hotel | Terms such as cancellation (below). | Optional |
| expires_at | Hotel | How long the session, its quoted price and any room hold last. | Optional |
| continue_url | Hotel | Where the guest finishes when the agent can't. Required when the status is requires_escalation. | Optional |
| confirmation | Hotel | The reservation number once completed, with an optional PIN and link. Required when the status is completed. | Optional |
| id · status · currency · links | Hotel | The 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
Cancellation, as data
Each cancellation policy carries one of three well-known labels, plus a written description that must not contradict it.
Cutoff times and penalties are in the written description, not in fields.
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.
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
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 for 2026-12-08
Planned for 2027-03-30
Proposals, no release
- #1065proposalNon-200 responses documentation consistency
- #1066proposalLodging
- #991proposalCorporate negotiated-rate entitlement for lodging
- #986proposalWhere a stay id comes fromWhether 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.
- #953proposalTraveler identity fieldsStandard names for date of birth, nationality, country of residence and gender on guest and booker.
- #955proposalLocal currency at the propertyShow charges paid at the hotel in its own currency, beside the converted amount.
Source: milestones, pull requests and issues labelled area:lodging, Universal-Commerce-Protocol/ucp, synced 22 Nov 2026
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.
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).
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.
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.
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.
- dev.
ucp. draftlodging. booking - dev.
ucp. draftlodging. policy. cancellation - dev.
ucp. 2026-08-25common. payment. terms - dev.
ucp. 2026-08-25common. location. lookup
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.
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
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
- #986, where a stay id comes fromopen, filed 22 Oct 2026
- Lodging Booking, draft specificationucp.dev/draft
- Lodging schemas on mainsource/schemas/lodging
- PR #780, booking capability and cancellation extensionmerged 24 Sep 2026
- #858, design questions left from #780open
- #543, Lodging charterclosed 10 Aug 2026
- Lodging Tech Council membersdiscussion #714, 11 Aug 2026
- Draft announceddiscussion #864, 25 Sep 2026
- Release 2026-08-25current release
- Book a room over UCP: a hotel test store in Playground 0.17.0/blog/playground-0-17-0-hotel-test-store-lodging-booking
- UCP Lodging Is Merged: What Changed on the Way to the Spec/blog/ucp-lodging-booking-merged-draft-spec
- A Room Is Not a SKU — UCP's First Lodging Capability Is in Review/blog/ucp-lodging-booking-capability
- UCP for Lodging Just Got a Technical Council. Here's Who's On It — and What They Have to Build./blog/ucp-lodging-technical-council-formed
- UCP for Lodging Just Got a Charter — and a Phased Roadmap. Here's What It Commits To./blog/ucp-lodging-charter-roadmap
- UCP for Hotels: A Hotelier's Guide to Agentic Booking/blog/ucp-for-hotels-hoteliers-guide
