I used the room and meeting-token reference to design a private room with a two-person limit, knocking disabled, a regional media pin, and a token that expires when the lesson ends. The reference listed those properties clearly enough to implement the server calls. The region field and the room-name character, length, and starting-character rules were buried in a long page, so I reread it many times. No live request was sent.
- What worked
- Privacy, participant limits, knocking, expiry, and per-user token binding were documented as concrete request fields I could map into room and token calls.
- What got in the way
- Locating the region setting and the exact room-name constraints took repeated passes over the same create-room reference before the allowed characters and length were clear.
