Authentication
All reservations endpoints require authentication via JWT token stored in theaccess_token cookie. The token is automatically obtained when a user logs in and must be included in all requests.
Base URL
Available Endpoints
Create Reservation
Register a new reservation in the system
List Reservations
Get all registered reservations
Update Reservation
Update an existing reservation
Delete Reservation
Delete a reservation from the system
Reservation Status
Reservations can have one of the following statuses:EN PROGRESO- Reservation is in progressFINALIZADO- Reservation is completed
v_extras Format
Thev_extras field is a critical part of the reservations API. It must be sent as a JSON string (not a JSON object) representing an array of extra items.
Valid Formats
Extra Object Structure
The ID of the extra item
The quantity of the extra item
The additional value/cost of the extra item
Common Response Codes
Request completed successfully
Validation error in the sent data
Token not sent or invalid
Reservation not found
Dates are occupied or not available
Internal server error
Date Validation
All reservation endpoints enforce that the end date (v_end_date) must be greater than the start date (v_init_date). Requests that violate this rule will be rejected with a 400 error.