Bind the session’s seat-member roster
Bind the session’s seat-member roster
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Headers
The passenger-session locator (a within-tenant locator, never a trust assertion). A missing or key-unsafe value is rejected 400 before this handler runs.
Request
Optional flight binding: the flight-instance identifier this session belongs to, matching an
identifier registered through the flight-context write endpoint. When present, the session is
bound to that flight and flight-aware reads (remaining flight time, the flight’s active
catalog) resolve through the binding, replacing whatever flight the session was bound to
before. When omitted, the session is left with NO flight context: any binding an earlier call
made for this session is removed, and reads behave as they do for a session that never named a
flight. Each call therefore sets the session’s flight context in full — it is never merged
with an earlier call’s. At most 128 characters, and control characters are rejected; a
rejected value is never echoed back in the error. Check flightBindingApplied on the response
to confirm the binding took effect.
Response
The server-resolved tiers, in the same order as the request’s members — echoed for display only, never trusted back.
Whether the flight-context outcome this request asked for is now in effect. True when the
session is bound to the flightInstanceId the request supplied — or, when the request omitted
it, when any binding an earlier call left on this session was removed. False means the flight
step did NOT take effect and the session’s flight context is unchanged from before this call:
results are not narrowed to the flight you named, or a flight bound by an earlier call may
still narrow them. The seat roster above is bound either way — a flight-context failure never
fails the request — so repeat the call to re-apply it.