Move a booking to another time
Moves the whole booking — every ticket on it — to the time that starts at startDate + startTime, one of the slots from the schedule call. All of it moves or none of it does; tickets, quantities and price stay as they are, and no new order or receipt is created. No email is sent: show the answer as the confirmation; the shopper’s existing e-tickets show the new time from now on. Choosing the current time changes nothing and answers 200. Requires the account token.
Authentication
Account token, browser-safe. Obtain one from POST /api/account/session with the 6-digit code POST /api/account/login emailed to the shopper; valid 30 minutes, for one store and one proven email, and it reads only that account’s own data. Sent as Authorization: Bearer <token>. Not interchangeable with the BearerAuth client token in either direction.
Path parameters
From GET /api/account/bookings.
Headers
Identifies which store this request is for. Required on every store-scoped route. It is not authentication and not a secret — it grants no privileges and is safe to send from a browser. You receive the value once your Entria backend has been created and configured. Missing header returns 400; an unknown store returns 404.
Request
Response
The move is done: the booking at its new time, in the same shape as in the list — the data for a success page. Its reservationToken usually differs from the one in the path: use the new one from now on.
Identifies the booking in the schedule and reschedule calls. It changes when the booking moves: take it from the latest list or reschedule answer.
Why it cannot move; empty when it can. reasonCode is MIXED_TIMES (parts of the booking are at different times, so it cannot move as one), or the ticketing system’s own code: CUTOFF_PASSED, ALREADY_ADMITTED, SLOT_PASSED, TICKET_BLOCKED, TICKET_EXPIRED, NOT_CONFIGURED, NOT_ALLOWED and others it adds. Can be empty for a booking that cannot move, when the system gave no reason.