This folder contains the maintained backend documentation for the Roomies API and runtime architecture.
roomies_project_plan.md— product goals, persona model, and phase statusImplementationPlan.md— implementation inventory, conventions, route surface, and codebase statusAPI.md— API entrypoint, transport rules, shared response conventions, and links to feature docsTechStack.md— runtime, database, queue, storage, validation, and operational decisionsDeployment.md— Azure-focused deployment and rollout guidance
Feature-level API documentation lives in docs/api/.
api/conventions.md— shared response envelopes, auth failures, pagination, and example conventionsapi/auth.md— registration, login, refresh, OTP, sessions, logout, and Google OAuth flowsapi/profiles-and-contact.md— student and PG owner profiles, contact reveal, and verification document submissionapi/properties.md— property CRUD and ownership rulesapi/listings.api.md— listing search, CRUD, lifecycle changes, saved listings, preferences, photo flows, and listing-scoped interestsapi/interests.md— interest request creation, dashboards, and transition state machineapi/connections.md— connection dashboard, detail, and two-sided confirmationapi/notifications.md— notification feed, unread count, and mark-read modesapi/ratings-and-reports.md— ratings, public reputation views, and rating report submissionapi/admin.md— verification queue, report moderation, user lifecycle actions, rating visibility controls, and platform analyticsapi/health.md— dependency health probe behavior
- Treat the route files in
src/routes/as the authoritative endpoint list. - Treat the validators in
src/validators/as the authoritative contract for params, query, and body shape. - Treat service-layer
AppErrorbranches as the authoritative source for documented business-rule failures. - Keep
API.mdas the front door and keep the feature-level detail insidedocs/api/.