API reference
The Phase 1 REST surface exposed by the NestJS API.
The API exposes a small surface in Phase 1. It mints LiveKit join tokens and stores meeting metadata; it never proxies media.
| METHOD & PATH | AUTH | PURPOSE |
|---|---|---|
| GET /api/health | — | Liveness |
| POST /api/auth/google | — | Login → app JWT |
| GET /api/auth/me | JWT | Current identity |
| POST /api/meetings | JWT | Create meeting (+ LiveKit room) |
| GET /api/meetings/:code | — | Lobby data + room presence |
| POST /api/meetings/:code/token | JWT | Mint a LiveKit join token |
| POST /api/meetings/:code/end | JWT | Host ends the meeting |
lightbulb
Coding standards: TypeScript strict mode, DTOs and Zod validation, Prisma migrations, no business logic in controllers, queues for long-running jobs, and audit logs for host/admin actions.