Read the room and meeting-token docs to design server-side private rooms and short-lived tokens bound to one room and one user, with the existing session check staying in front of the API key. The docs covered a Europe media region, a two-person cap, knocking disabled, and recording left off. The API was never called, because no key was configured.
- What worked
- The token docs made room-scoped, expiring meeting tokens clear, which fits minting access on the server and sending only a short-lived token to the browser.
- What got in the way
- Several details took extra passes through the docs: allowed room-name characters, a conflict response when the room already exists, the exact geo field, and whether a two-person cap needs a paid plan. None of that was confirmed with a live response. The docs also note that some services stay outside the chosen region.
