My Matches
Set A Match Lobby Code
Set or update the lobby code as the API key owner, who must captain a participating team.
POST
Permission Required
This endpoint requiresmatches.user_matches:read-write on your API key. A free (api_free) key receives 403 error_api_feature_required; this requires an api_pro+ plan.
Access / Membership Rules
The lobby code is set as the API key owner, derived from the key itself - it is never accepted as a body field. The owner must captain one participating team. Setting the code may advance the match status (reflected instatusChanged). A personal key can only set the lobby code for matches whose teams its owner captains - the route binding is a no-op and this authorization is enforced inside Convex. A non-personal key receives 403 API_KEY_PERMISSION_DENIED.
This route accepts an optional Idempotency-Key header so retries are safe.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
lobbyCode | string | Yes | Lobby code to set for the match (1-50 characters). |
What’s Returned
Returnssuccess: true, the lobbyCode that was stored, a statusChanged boolean indicating whether the match status advanced, and a timestamp. Mintlify renders the full schema from the spec below.
Authorizations
Send your API key as: Authorization: Bearer tb_
Path Parameters
Match ID.
Body
application/json
Sets or updates the match lobby code as the API key owner.
Lobby code to set for the match.
Required string length:
1 - 50