Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[Feature Request] Minimal Voice Activity Endpoint (active/inactive + mute and streaming only) #7888

Unanswered
N0edL asked this question in API Feature Requests & Ideas
Discussion options

Summary
There is currently no way for an application to know if a user is active in any voice call (guild or DM) without joining every guild and listening to gateway events. DM/private calls are not exposed at all.

What we need
A minimal endpoint that returns only:

  • If a user is in any voice call (active/inactive)
  • If the user is muted

No channel IDs, no guild IDs, no participants. Just a simple active/mute status.

Why this matters
We are building MetaGuard for FiveM roleplay servers to prevent metagaming.

  • The system only needs to know if a user is currently in a call.
  • No sensitive data is required.
  • This would help enforce fair play while still respecting privacy.

Current limitations

  • GET /guilds/{guild_id}/voice-states/{user_id} requires the bot to be in every guild.
  • Gateway events only work for guilds where the bot is present.
  • DM/private call activity is completely invisible.

Proposed solution
Introduce a minimal endpoint, for example:

GET /users/{user_id}/voice-status

Response example

{
 "active": true,
 "muted": false,
 "streaming":false,
}

This would still respect privacy while enabling important use cases such as anti-metagaming systems, fair-play enforcement, or simple activity tracking.

You must be logged in to vote

Replies: 2 comments 3 replies

Comment options

Instead of Discord, they can start calling each other elsewhere

You must be logged in to vote
1 reply
Comment options

yeah short of screen and audio monitoring software this system is pretty much DOA, and even then it can (and will) be worked around

Comment options

This can be used to potentially stalk users even in small cases. We do not need this kind of feature. I don't need a bot to be able to query if I'm in a call even if I'm showing as invisible.

That's a no from me dawg.

You must be logged in to vote
2 replies
Comment options

OAuth2 Scopes?

Comment options

that thing people definitely take their time reading instead of just spam clicking Okay?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

AltStyle によって変換されたページ (->オリジナル) /