Try And Attempt Admit

This endpoint combines the [tryAdmit](try-admit) and [admitToken](admit-token) 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. <b>⚠ HTTP 200 does NOT mean admission was completed — always inspect `admittedTokens`</b> <br>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. <b>`admittedTokens` is non-empty</b> — Admission was completed automatically. The gate should open. <b>`admittedTokens` is empty</b> — 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`](admit-token) or [`/tryAndAttemptAdmit`](try-and-attempt-admit), 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). <b>When will `admittedTokens` be empty?</b> <br>Automatic admission is skipped whenever the server cannot unambiguously resolve the admission intent. Common scenarios include: - <b>Wallet containing multiple valid assets</b> — 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. - <b>Group ticket with unconfirmed attendee count</b> — A group ticket requires the operator to confirm the actual number of attendees before admission can proceed. Call [`/admit`](admit-token) with the token and the confirmed quantity. <b>Membership allowing guests</b> <br>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`](admit-token) with the corresponding admit token and the quantity of guests to admit for the selected category.

Authentication

x-np-api-keystring
API Key authentication via header

Path parameters

tenantstringRequired

Your Entra Tenant ID. More details.

environmentstringRequired

Your Business Central Environment. More details.

companystringRequired

Your Business Central Company. More details.

Headers

x-api-versiondateOptional

Used for API versioning. More details.

Request

This endpoint expects an object.
referenceNumberstringRequired
The number sent to speedgate to open the gate
scannerIdstringOptional
A human friendly unique code that identifies a specific speedgate.
admissionCodestringOptional
A unique code that identifies a specific admission.

Response

Returns the try result including type-specific details and any tokens that were automatically admitted.

tokenUUID
A unique token that identifies a specific admission request
referenceNumberTypeenum
The type of reference number that was identified.
admittedTokenslist of objects
memberCardobject or null
Details of a member card and its guests
ticketobject or null
When attempting to admit a ticket, some ticket details should be provided.
walletobject or null
Details of a wallet and its tickets
docLxCityCardobject or null
ticketRequestobject or null