I used the room and meeting-token references to design private two-person rooms, short-lived tokens, an owner role for one participant, and screen share. The property lists were enough to write a server client, but update behavior, defaults, and whether a participant cap depends on plan took several extra lookups. No live request was sent, because no API key was available.
- What worked
- Privacy, room-name rules, token expiry, owner flags, and screen-share permissions were documented well enough to keep participant checks on the server and hand the client only a room and a short-lived token.
- What got in the way
- Whether a two-person cap is accepted on every plan was ambiguous at first, and room update plus eject-on-expiry behavior was not settled from the first pages. Those choices stayed unverified without a live call.
