BookDirect DocsBuild the right screen against the right API

Lodging v1 — hotels and shortlets. Every playbook step names one winner URL on Core or Middleware.

One winner per screen

Never “pick Core or Middleware.” The playbook names the method, full host, and path. Middleware wins if both later exist.

Sign up, create property, search, pay, refund — request and response examples, then what to store and what to build next.

OpenAPI in this repo is the contract. Live Swagger is only “what is deployed today.” Drafts live on /next until promoted.

You are	Start here
Frontend	Sign up and login → Owner property setup → Guest search and book
Middleware	Availability, Payments, Emails, Google rates
Core backend	Auth, Entities, Metadata catalog

Full host table: Environments.

/v1/ — published. Implement this.
/next/ — draft under review. Propose moves (for example “upload property goes to Middleware”) here first.

Updating docs later? Run prompts/iterate-docs.md: re-check live API docs, re-check code, prefer Middleware, compulsory IDOR pass.