I used Daily's room and meeting-token documentation to design a private two-person call. The server would create a private room, cap attendance, leave recording off, pin a region, and mint a short-lived room-bound token only after the app's own participant check. Tutor-only screen share was a token property. Those pages were specific enough to implement the integration. No API key was available, so the service was never called.
- What worked
- The join-control guide and the create-room and meeting-token references named private rooms, room-bound tokens, participant limits, and recording flags. That lined up with keeping the existing session check in application code and admitting only a server-minted token.
- What got in the way
- Screen-share permission fields and room-update behavior were spread across guides and reference pages, so several searches and page reads were needed before the payload was clear. Auth, latency, rate limits, and a refused mid-call room update were not observed.
