Thanks — I’m responding about expiring a LiveKit room ID or binding a time-based expiry. Quick summary: you cannot directly set an expiry on a Room ID. You can achieve the behavior you want with one of these options: • Set an automatic room close using

empty_timeout

when creating the room (room closes after being empty for that many seconds). Example: create with

emptyTimeout: 60

to close 60s after last participant leaves. • Manually delete the room via the server API when your meeting ends (

DeleteRoom

) — this immediately makes the Room ID unusable. • Restrict join access by issuing access tokens with a short

exp

claim so new joins are blocked after the token expires (this does not disconnect already-connected participants). Which of these do you want help implementing? Tell me: 1. Which SDK/language you’re using (Node, Python, Go, etc.), and 2. Do you prefer automatic close, manual deletion at meeting end, or token-based join restrictions? I’ll provide the exact code/snippets and steps for your chosen approach. Sources: Avoiding Room ID Reuse When Re-Creating Rooms With the Same Name | Job lifecycle | LiveKit docs | server-sdk-kotlin | livekit/livekit_composite | DeepWiki