Release a reservation
Use Case Description
In some booking flows, the user may abandon the process or cancel the operation before finalizing the appointment. Instead of waiting for the full 15-minute timeout, the integration can call this endpoint to release the reserved slot instantly.
This is particularly useful in:
High-traffic environments where slot availability is critical
Optimizing scheduling in international or high-demand use cases
Reducing artificial slot blocking caused by user abandonment
For a full reference of each endpoint interaction please consult the Qmatic Cloud Appointments API - API Reference.
Note! The endpoint can be used until the Appointment status turns into FINALIZED or CONFIRMED status. Once the appointment gets confirmed Cancel an appointment endpoint should be used to delete it.
API Endpoints
Release a reservation
/external/v1/reservations/reservations/{appointmentId}
Attributes
Name | Type | Required | Description |
|---|---|---|---|
X-TENANT-ID | string | yes | The tenant id to use for this operation. The tenant id must be the same as an existing system Id. |
AppointmentID | string | yes | Appointment ID (GUID) |
Response schema
Code 204 -Reservation released