Skip to content

How to build: Reservations and Inventory ​

implemented /extranet/reservations, /extranet/properties/[id]/reservations.

Middleware Backend · winner · live

GET https://middleware-dev.bookdirect.live/api/v1/nellalink/reservations/property/{propertyId}

GET https://middleware-dev.bookdirect.live/api/v1/nellalink/reservations/{id}

PATCH https://middleware-dev.bookdirect.live/api/v1/nellalink/reservations/{id}/status

Query status: pending | confirmed | checked_in | checked_out | cancelled.

json
{ "status": "confirmed" }

Allowed transitions: confirmed, checked_in, checked_out, cancelled. JWT must own the property (or Core role).

ScreenHow to build
Inventory Calendar / Availability ResultsAvailability POST .../availability/check
Blackout Dates / Minimum Stay Rulesto implement — recommend on Middleware, do not only filter in the UI
Reservations / Reservation DetailsGET list + GET by id
Create Manual BookingPOST .../nellalink/bookings (see Dashboard)
Modify Reservationguest PUT .../bookings/{id} while pending; host uses status patch
Cancel ReservationPATCH { "status": "cancelled" } — refunds folder still missing for captured money
Pending Bookings?status=pending
Booking Enquiries / Booking Reportsto implement

API-first. Middleware Backend wins over Core Backend when both exist.