Skip to content

Application Activity-instance verification

inspect_application_activity_instance belongs to the connector toolset and verifies one Discord Activity session owned by the pinned current application. Supply the opaque instance ID from the Activity client plus the exact guild and channel IDs where that client expects the session to be running. An optional exact user ID asks only whether that user appears in the session. The tool accepts no caller-selected application ID, private-channel target, participant query, name, token, URL, or write instruction.

The connector verifies its configured application and bot identities, applies ordinary exact guild and channel read policy, then calls Discord's Get Application Activity Instance endpoint with the pinned application ID. Discord requires the bot token for the same application. A successful response must repeat the expected application and opaque instance IDs, carry a valid launch ID, and identify the exact expected public guild-channel location. A private-channel location, different guild or channel, duplicate or malformed participant ID, unsupported response shape, or mismatched identity fails closed without returning the remote evidence. Discord's 404 response becomes a structured inactive or unavailable result; other failures remain errors rather than being interpreted as absence.

An active result returns the verified application and bot IDs, exact expected location, launch ID, participant count, optional boolean answer for the one supplied user, and count-only unknown-field evidence. It never returns the participant list, display names, profiles, the location's opaque ID, or raw Discord objects. No result enters a cache, Gateway buffer, activity record, operation receipt, telemetry payload, or persistent file. The check is one transient snapshot, not an authorization result, durable membership assertion, session launch, Activity join, or voice connection. Discord's multiplayer Activity guide describes how Activity clients coordinate instance and location state.

Canonical source: docs/reference.md

Documentation generated for guildcontrol@0.0.0. Canonical source and edit history remain in the public repository. GuildControl is an independent project and is not affiliated with or endorsed by Discord Inc. Discord is used only to identify the platform that GuildControl connects to.