List the logged-in shopper’s upcoming bookings, and which can be moved
Lists the upcoming bookings registered to the account token’s email. Each says whether it can move to another time right now (reschedulable) and, if not, why (reasons) — for example used, too close to its time, not allowed by the venue, or with parts at different times. Show the ones that cannot move too (with a “contact the venue” hint), so no booking seems to vanish; only reschedulable ones open GET /api/account/bookings/{reservationToken}/schedule. Past bookings are left out. A booking moves as a whole: its tickets and quantities stay as they are and nothing is charged or refunded. The newest 25 bookings are checked; truncated: true means there were more. Requires the account token from POST /api/account/session.
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.
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.
Response
The upcoming bookings, each marked reschedulable or not. An empty list means there are none.