Find active tickets by email
Authentication
Headers
Query parameters
Response
Active tickets found by an email — expired and already-consumed tickets are excluded, so an empty list does not mean the email never had tickets
Active tickets found by an email — expired and already-consumed tickets are excluded, so an empty list does not mean the email never had tickets
Looks up active tickets registered to an email — the rebooking check: is there anything to rebook before letting a change proceed. Blocked and expired tickets are excluded (BC’s activeOnly, pinned upstream rather than exposed as an option); already-admitted tickets are NOT excluded, so check admission state before treating a result as rebookable. No match is a 200 with an empty tickets array, not a 404.
Short-lived access token for endpoints that return personal data. Obtain one from POST /oauth/token (RFC 7523 JWT-bearer), signing the assertion with the private key of the key pair registered for your store. Sent as Authorization: Bearer <token>. This is separate from the x-entria store header, which is still required.
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.