Resources

Handle Expedia Group reservation changes without leaving your system

Written by Hidde Straat | Sep 9, 2026, 2:49:05 PM

A guest never arrives. Another asks to cut two nights off the end of their stay. A third stays an extra night that was agreed at the door but never made it onto the booking. None of these are complicated problems. What makes them expensive is the workflow around them: someone opens Expedia Partner Central, finds the reservation, makes the change by hand, and then reconciles the figures later. When the change falls outside what the extranet allows, that becomes a support ticket and a wait.

Reservation Updates remove that detour. Cancellations, date changes and rate corrections for Expedia Group reservations can be made through the NextPax Supply API, in the system your team already works in.

What you can do

Cancel no-shows. When a guest does not turn up, you can close out the reservation through the API rather than logging into Partner Central.

Change travel dates and rates together. Early departures, extended stays and agreed rate corrections are applied to the reservation itself. When you change arrival or departure dates, the new stay price and rental price go with them in the same request — the dates and the pricing cannot drift apart, because the API will not accept one without the other.

Process guest-requested cancellations. Cancel through the API and let the cancellation policy on the reservation determine what is due.

Why the post-booking half matters

Most connectivity handles the first half of a reservation's life well. Bookings arrive, availability closes, confirmations go out. The awkward half comes later, once a stay has started and the reservation no longer matches reality.

That is where manual work concentrates, and where two records start to disagree — not because anyone made a mistake, but because a change was agreed in one place and recorded in another. Every extranet login is a context switch, and every manual adjustment is a chance for the drift to widen. Handling these changes through the same integration you already use for everything else means one fewer exception for your team to remember, and less back-and-forth with Expedia Group support over changes that could have been made directly.

Getting started

Reservation Updates are part of the Expedia Group connection through NextPax.

Already connected to Expedia Group through us? Your development team will find the endpoints, request formats and field references in the NextPax Developer Portal.

See the documentationhttps://developer.nextpax.app/

Not yet distributing to Expedia Group, or want to talk it through first? Tell us which channels you work with and we will walk you through what enabling this involves for your setup. One of our team will come back to you within one working day.

Talk to our teamhttps://nextpax.com/contact