The control plane’s admin API is gRPC, package moqom.admin.v1. The Go and Rust SDKs wrap
it; you can also generate a client from the protos in any language gRPC supports.
Endpoint
api.moqom.cloud:443 (TLS)
Auth
gRPC metadata authorization: Bearer mqk_… with a backend key
Scope
Every request names a tenant; it must be the key’s tenant
Services
Rooms, Moderation, Tokens, Events, RelayPools
Relay keys are refused by every admin service (PERMISSION_DENIED).
Create a room. room is your own name for it. Optional owner_username, policy, starts_at (creates it SCHEDULED).
GetRoom
GetRoomRequest → Room
Read one room.
ListRooms
ListRoomsRequest → ListRoomsResponse
Page through rooms, optionally filtered by lifecycle[].
UpdateRoomPolicy
UpdateRoomPolicyRequest → Room
Change policy on a live room. Use update_mask; absent means all fields. Tightening applies immediately to everyone. residency_zone is immutable. e2ee can only be required; E2EE_POLICY_OPTIONAL is refused.
CloseRoom
CloseRoomRequest → Room
End the room for everyone with a ModerationCode. Idempotent.
{minimum_age, require_verification} — with verification required, tokens must be minted with age_verified
recording
ALLOWED, REQUIRED (a hosted recording starts with the room and can’t be stopped while it is open), PROHIBITED
residency_zone
Where the room’s data (including derived data) may live. Immutable.
max_participants
Device limit; 0 = unlimited
stage_slots
Simultaneous video publishers (default 8)
watchdog_limit
Watchdogs that may attach (default 8)
e2ee
Always E2EE_POLICY_REQUIRED; UNSPECIFIED means the same, and a room read back always states it. E2EE_POLICY_OPTIONAL is deprecated and refused on CreateRoom and UpdateRoomPolicy. Carried to devices as the e2ee claim in client tokens. See End-to-end encryption.
The public keys MOQOM’s relays verify tokens with. Rotated without deploys.
SetAppleSignIn
Turn on Apple sign-in hosted by MOQOM for the tenant: Apple team ID, bundle IDs, which existing rooms, and the publish grants. It never grants moderation or creates rooms. Needs a backend key.
token (sealed and opaque, passed by the client at
session setup), expires_at, identity (with the device already derived), key_id (matches a
VerificationKey.key_id), direct (the room’s point-to-point policy), relays (the relay
addresses a token for a private relay pool must dial; absent for
the shared fleet). For a private tenant the token also carries a pool claim naming its pool;
the token is sealed, so clients never read it. Hand these to the device
as the token response; it can’t read them from
the token.
Failure modes:
Code
Cause
INVALID_ARGUMENT
Missing device_thumbprint, bad username, lifetime above 15 minutes
PERMISSION_DENIED
Asking for capabilities, ownership or publish rights the key cannot grant
NOT_FOUND
The room does not exist
FAILED_PRECONDITION
No credit (payment required / insufficient credit), room ended, or room requires age verification
A relay pool is a set of relays that carries only your tenant’s traffic. See
Private relay networks. Every RPC here needs your owner key, a
backend key; mint and readonly keys are refused with
PERMISSION_DENIED.