---
title: "Try And Attempt Admit"
method: POST
path: "/{tenant}/{environment}/{company}/speedgate/tryAndAttemptAdmit"
tags: ["speedgate > Speedgate"]
---

# Try And Attempt Admit

`POST /{tenant}/{environment}/{company}/speedgate/tryAndAttemptAdmit`

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.

## Path parameters

- `tenant` string, required — Your Entra Tenant ID. [More details.](/paths#1-tenant)
- `environment` string, required — Your Business Central Environment. [More details.](/paths#2-environment)
- `company` string, required — Your Business Central Company. [More details.](/paths#3-company)

## Headers

- `x-np-api-key` string, required
- `x-api-version` string, date — Used for API versioning. [More details.](/apis/versioning)

## Request body

- TypesCompositeTryAdmitRequest — unresolved $ref

## Response `200`

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

- TypesCompositeTryAndAttemptAdmitResponse — unresolved $ref

---

[API](https://skmtc.dev/navipartner/apis/api-reference.md) · [All operations](https://skmtc.dev/navipartner/apis/api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/navipartner/api-reference/revisions/679ad9860a08/schema)