Get the Discord bot's state
/api/health/discord-botWhere the Discord bot is: NotConfigured, Connecting, Connected, Disconnected or Failed; null when this server runs no bot. The word alone, for the Integrations page, so it needs ManageSettings rather than ViewOperationalLog. The bot's errors and counts stay in the sync health read.
Needs the ManageSettings permission.
An API key, made on Settings, API keys. Every key starts with mbk_.
In: header
Response Body
application/json
application/problem+json
application/problem+json
curl -X GET "https://example.com/api/health/discord-bot"{ "state": null}Get instance activity GET
How many people were in the group's instances, moment by moment, over the last `day`, `week` (the default), `month` or `all` recorded time. Built from VRChat's own head counts -- `userCount` from each open group instance's page, read about every thirty seconds -- so it covers instances no moderator's companion was in. A count is kept only when it changes, so the series is a staircase and each point holds until the next. Long ranges are thinned to at most about 500 points: the window is cut into equal steps and the last reading in each is kept. `instances` is how many instances had a count at that moment. Needs the `ViewAnalytics` permission.
Get VRChat gate health GET
Whether Modbot is reaching VRChat, and whether that is a problem. `status` is the load-bearing field. RateLimited and WafBlocked both stop traffic and look identical from outside, and they mean opposite things: a cold stop is spec 4.3.1 working as designed and recovers on its own, while a WAF block needs an egress proxy and will not clear by itself. Available to any signed-in account. A moderator whose action did nothing needs to be able to tell waiting from broken.