Get audit log filters
/api/audit/filtersThe type list is already narrowed to the caller's permissions, so the SPA offers only what the server would answer. The actor list is the recent actors in the visible history — a filter control, deliberately not a member list.
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/audit/filters"{ "types": [ { "value": "string", "label": "string", "category": "Moderation", "shows": [ "string" ] } ], "sources": [ "string" ], "actors": [ { "platform": "string", "id": "string", "name": null, "actions": 0 } ], "canViewModeration": true, "canViewOperational": true}Get entries around an audit log entry GET
What else happened around one entry: the same actor's entries and the same person's entries, up to five either side, each list newest first with the entry itself in its place. `byActor` is null when nobody is named for the entry; `aboutSubject` is null when the entry is not about a person. Only types this account may read are listed, and an entry it may not read answers 404.
List recorded bans GET
Bans Modbot has recorded — not the group's ban list. Derived from ban and unban facts, which come from VRChat's group audit log. It therefore covers the period since this deployment first synced, bounded by whatever VRChat's own audit-log retention still held at that moment — a group with three years of bans and a week-old Modbot has a week of them here. `coverage` carries that window and callers must show it. A full ban list needs a sweep of groups.bans, which is not built. Needs the `ViewAuditLog` permission.