Clan Hub (lobby, roles, presence)

Moderation, join modes, invites, profile, activity — pairs with clan chat & clan voice

Clan Hub API (lobby / moderación / presencia)



Clan lobby tab in the game client: roles, invites, join modes, profile editing, member presence, and activity feed. Multi-game safe — all routes are scoped to the authenticated user’s game_id.

Developer page: Clan Hub API
Related: Friends Chat (POST /chat/conversations/clan), Match Voice (POST /voice/rooms/clan)
Postman: Extended collection → folder Friends and Clans (base CRUD; add Hub routes as needed)

Auth: Authorization: Bearer {game_session_token} (same as shop, inventory, chat).

Roles in JSON: leader | officer | member (database stores officers as co_leader).

Roles en API: leader | officer | member (DB: co_leader = officer).

Permisos



GET /api/v1/clans/permissions → permissions_by_role

Edición del clan



MétodoRutaPermiso
PATCH/clans/{id}edit_clan — name, tag, description, max_members, logo, banner_url, accent_color, motd, pinned_announcement, is_public
PATCH/clans/{id}/join-modeset_join_mode — body: { "join_mode": "open" \"invite_only" \"closed" }

Entrada



join_modeComportamiento
openPOST /clans/{id}/join directo
invite_onlyPOST /clans/{id}/join con invite_token, o POST /clans/{id}/applications + approve
closedSolo invitación (POST /clans/{id}/invites → token → join)

MétodoRuta
POST/clans/{id}/invites — { "invited_user_id": optional } → token, invite_url
POST/clans/invites/accept — { "invite_token" }
POST/clans/{id}/applications — solicitud (invite_only)
GET/clans/{id}/applications — pendientes (officer+)
POST/clans/{id}/applications/{requestId}/review — { "action": "approve" \"reject" }

Moderación



MétodoRuta
POST/clans/{id}/members/{userId}/kick
POST/clans/{id}/members/{userId}/ban — optional reason, expires_at
PATCH/clans/{id}/members/{userId}/role — { "role": "officer" \"member" }
POST/clans/{id}/transfer-leadership — { "new_leader_user_id" }
POST/clans/{id}/dissolve — owner only

Hub UX



MétodoRuta
GET/clans/{id}/presence — online \in_match \offline, last_seen_at, match_key
GET/clans/{id}/activity?limit=30 — feed (member.joined, member.kicked, clan.updated, …)

in_match usa Redis voice:match:g{game_id}:user:{id}:active (set al unirse a partida). La misma lógica está en GET /api/v1/friendships/presence para amigos aceptados (ver Chat API).

Migración



php artisan migrate