Vehicle Sessions

Travelport Universal API offers session abilities for vehicle booking. The session workflow is intended to be granular or incremental, allowing the user to validate or branch based on success or failure. Using this workflow, you can add vehicle segments within a session, so that the consuming application can more easily process warnings and errors, and you can coordinate the workflow in a succinct fashion.

This workflow lets API consumers modify a vehicle reservation within an active session, review the pricing impact of the change, and then commit it (End) or discard it (Ignore) with no penalty for discarding. adds transactional, session based modification with explicit commit or rollback control. It adds transactional, session-based modification with explicit commit or rollback control.

Notes:

• Galileo (1G) only. A request sent for an unsupported provider returns an error.

• Schema v55 and greater. Reservations created with earlier schema versions can still be modified using the v55 transaction. For example, a reservation created in v52 can be modified using the v55 workflow. Only the session based modify transaction itself is restricted to v55. U

Provided capability

• Stage a vehicle modification within an active session, rather than committing it immediately.

• See whether the modification changes the reservation price before you decide to keep it.

• Commit the change (End) to save it to the reservation, or discard it (Ignore) to retain the original reservation unchanged.

• Apply a new vehicle rate code during modification, which is not available through the existing UniversalRecordModify/Vehicle transaction.

BookingVehiclePnrElement provides a safer, more transparent modification: travelers and downstream systems can review price and policy impact before a change is persisted, reducing the need for cancel-and-rebook.

Workflows

Vehicle Booking Session Transaction Workflow

Booking Start	Begin your session with a Booking Start request.
Booking Display	Display the current state of the booking.
Booking Vehicle PNR Element	Stage the vehicle update (one element).
Booking End	Close the session with one of: BookingEndReq / SessionActivity="End" to commit the change, or BookingEndReq / SessionActivity="Ignore" to discard the change.
UniversalRecordRetrieve	Retrieve and validate the final reservation state.

Best Practice: Always close a session explicitly with End or Ignore. Leaving sessions open can create locked sessions, stale transactional state, and “accessed by another transaction” errors.

When to Use This Workflow

Recommended for

• Small, targeted reservation modifications.

• Pricing sensitive updates where the traveler must preview the price impact.

• Rate code modifications that require customer review.

• Single field changes such as a return date change or a rate code update.

Not recommended for

• Bulk modifications or large PNR restructuring.

• Multiple simultaneous update types.

• General purpose session booking flows.

For large scale changes, cancel the segment and rebook the reservation. This avoids session processing overhead, host limitations, and the added complexity of multi step modification, all of which become more likely as the size of the change grows.