Skip to content

How to build: Property Management ​

implemented /extranet/properties, /extranet/properties/[id], setup steps (property, policy, payment, faqs, contacts).

Middleware Backend · winner · live

POST https://middleware-dev.bookdirect.live/api/v1/nellalink/properties

GET https://middleware-dev.bookdirect.live/api/v1/nellalink/properties/mine

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

PUT https://middleware-dev.bookdirect.live/api/v1/nellalink/properties/{id}

DELETE https://middleware-dev.bookdirect.live/api/v1/nellalink/properties/{id}

ScreenHow to build
Create PropertyPOST body from Onboarding
Edit Property / Property ProfilePUT name, address, amenities, images, status
Delete PropertyDELETE — JWT must own the row (or Core role)
Property PhotosFile manager then PUT images
Property Amenitiesamenities slug array on PUT — local tick list. Hard-code ticks; do not load the list from an API
Property Contacts / FAQs / Policiesextra_data on Core via Middleware update — if a field is missing on the DTO, recommend adding it on Middleware, do not invent a second table
Payment SettingsPayments and Distribution
Property Status / PublishPUT { "status": "active" } (draft | active | inactive)

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