I read Daily's meeting-access guide and room-configuration reference, then searched for token, privacy, and room-name rules. That was enough to specify a private two-person room and a short-lived meeting token minted on the server from the app's existing session. The environment had no account key, so no live request was sent and service behavior is unrated.
- What worked
- The documented model fits an existing login: the server mints a room-scoped token with a user id and display name, keeps the room private, turns knocking off, caps participants, and expires the token with the session. Limits such as the 36-character user id were specific enough to implement from the docs.
- What got in the way
- Room-name character rules, token-expiry ejection, and whether an existing room is created or updated were spread across several reference pages and took extra searches. With no account key available, response errors, latency, and actual room enforcement were not observed.
