Change, remove legs or travelers from, replace travelers on, or cancel an issued train booking

Execute one operation on an issued train booking, confirming the estimatedTotalAmount from the preceding POST .../operation-quotes. operationType is change_datetime, change_itinerary, remove_legs, remove_passengers, change_travellers or cancellation. Removing a traveler who is the booking holder requires newHolderTravelerId, a traveler who stays.

Returns 201 when the operator completed it and 202 while it is still being confirmed (status: processing); read the booking until it settles. A total that moved since the quote returns 409 CHANGE_PRICE_CHANGED (or CANCELLATION_FEE_CHANGED): quote again and confirm with a new Idempotency-Key.

The Idempotency-Key header is required.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
Body Params
Headers

Client-generated idempotency key (UUID v4 recommended). Required on all booking mutation requests. Whether a repeated key replays the first response depends on the operation; see its description and the idempotency and retries guide.

Responses

202

The operation is still being confirmed

401

Missing or invalid authentication

404

Booking not found

409

The operator does not allow changing the booking now

410

The change search expired; search again

422

The selection does not fit the booking or the operator's rules (INVALID_CHANGE_SELECTION; details[0].reason says why)

503

Booking or train provider unavailable

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json