This endpoint combines the tryAdmit and admitToken steps into a single call, eliminating a network
round-trip for straightforward admissions. The server first resolves the reference number, then immediately attempts to admit the
resolved token if admission can be determined without operator input.
⚠ HTTP 200 does NOT mean admission was completed — always inspect admittedTokens
A successful HTTP 200 response only confirms that the reference number was recognized. Whether admission was actually carried
out must be determined by examining the admittedTokens array in the response.
admittedTokens is non-empty — Admission was completed automatically. The gate should open.
admittedTokens is empty — The reference number was recognized and one or more follow-up reference numbers may have been
issued, but admission could not be completed without additional operator input. The caller MUST follow up with a call to either
/admit or /tryAndAttemptAdmit, using either the issued token (if available) or a
reference number from this response, together with any additional information the UI has gathered from the operator (e.g., which
ticket to use or how many attendees to admit).
When will admittedTokens be empty?
Automatic admission is skipped whenever the server cannot unambiguously resolve the admission intent. Common scenarios include:
-
Wallet containing multiple valid assets — The wallet holds more than one asset that is eligible for admission at this gate
and the system cannot choose one on behalf of the operator. wallet.validToAdmit will be false. Present the wallet’s assets to
the operator, let them select the correct asset, then call this endpoint again with the selected asset’s reference number from
the operator response.
-
Group ticket with unconfirmed attendee count — A group ticket requires the operator to confirm the actual number of
attendees before admission can proceed. Call /admit with the token and the confirmed quantity.
Membership allowing guests
If the reference number corresponds to a membership, the member card itself may be admitted automatically (so admittedTokens
is non-empty). In that case, check the guests array for potential complimentary guests. Guests are not admitted automatically
because the system needs the operator to confirm which guests to admit. Call /admit with the corresponding admit
token and the quantity of guests to admit for the selected category.