---
title: "Confirm Slot By slotId"
method: PUT
path: "/partner/slot/confirmSlot/{slotId}"
tags: ["Partner::Slots"]
---

# Confirm Slot By slotId

`PUT /partner/slot/confirmSlot/{slotId}`

The slot confirmation endpoint allows partners to confirm or deny a reservation (exclusively for gyms that has the slot confirmation flag set as "true" -  [Update Place Configurations API](https://dev.totalpass.com/reference/put_partner-places-update-configs)) within 5 minutes of its creation.  This is particularly useful for scenarios requiring manual validation or approval, such as events that need additional confirmation before finalizing the reservation. Confirming slots ensures efficient and accurate reservation management. Through this endpoint, partners can:

  - Confirm a slot reservation, ensuring the user has a guaranteed spot at the event.
  - Deny a slot reservation, meaning the user will see the reservation as canceled in our app.

## Parameters

- `#/paths/~1partner~1slot/get/parameters/0` — unresolved $ref
- `#/paths/~1partner~1slot~1%7BslotId%7D/delete/parameters/1` — unresolved $ref

## Request body

- object
  - `state` 'confirmed' | 'denied', required — The state field represents the current status of the slot, indicating its condition after confirmation and is used to update the slot's status in the system.
  - `reason` 'reason_not_provided' | 'class_overbooked' | 'api_error' | 'denied_by_gym' | 'user_not_elegible' | 'monthly_limit_exceeded' | 'unavailable_spot' | 'user_already_in_class' | 'canceled_event' — The reason field is optional and is used to provide default additional information about the slot's status.

## Response `200`

Confirmed Slot

- object

## Other responses

- `400` — Bad Request
- `401` — unresolved $ref
- `404` — Not Found

---

[API](https://skmtc.net/totalpass/apis/token-use.md) · [All operations](https://skmtc.net/totalpass/apis/token-use/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/totalpass/token-use/revisions/bc65b4950c7e/schema)