Delete Reservation

​

Endpoint

DELETE /api/reservations/:id

​

Description

​

Authentication

​

Path Parameters

​

Response

​

Example Request

curl -X DELETE https://your-domain.com/api/reservations/res789 \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json"

​

Example Response

{
  "status": 200,
  "data": {
    "id": "res789",
    "deleted": true
  }
}

​

Error Responses

​

Not Found

{
  "statusCode": 404,
  "message": "Reserva no encontrada",
  "error": "Not Found"
}

​

Unauthorized

{
  "statusCode": 401,
  "message": "Token inválido o expirado",
  "error": "Unauthorized"
}

​

Use Cases

• Cancel an appointment
• Remove a reservation from the system
• Clean up test or outdated reservations
• Allow users to cancel their bookings

​

Important Considerations

​

Before Deleting

• Verify the reservation exists using Get One
• Check if the reservation has an associated payment that may need refunding
• Consider the professional’s cancellation policy
• Notify relevant parties (client and professional) about the cancellation

​

Alternative Approach

// Update status instead of deleting (if update endpoint exists)
const cancelReservation = async (reservationId: string) => {
  // Update the reservation status to CANCELLED
  // This maintains the record for historical purposes
};

​

Best Practices

• Implement confirmation dialogs in your UI before deletion
• Log deletion events for audit purposes
• Handle refunds if payment was processed
• Send cancellation notifications to affected parties
• Consider a “soft delete” pattern for business requirements

​

Related Endpoints

• Get One - Retrieve reservation details before deletion
• Create Without Payment - Create a new reservation
• Get By User - View all user reservations