List case files
/api/casesCase files, newest first -- everyone's, or one person's. Withdrawn case files are left out unless includeWithdrawn is true. Nothing is ever deleted, so a withdrawn one is still there to read; it just no longer counts as the write-up of its ban.
Needs the ViewProfile permission.
An API key, made on Settings, API keys. Every key starts with mbk_.
In: header
Query Parameters
Also accepted as userId.
int32int32Response Body
application/json
application/problem+json
application/problem+json
curl -X GET "https://example.com/api/cases"{ "cases": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "userId": "string", "displayName": null, "bannedAt": null, "auditEntryId": null, "authorUsername": "string", "reasons": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "label": "string", "isActive": true } ], "createdAt": "2019-08-24T14:15:22Z", "updatedAt": "2019-08-24T14:15:22Z", "withdrawn": true, "evidenceCount": 0, "liftedAt": null } ], "total": 0, "offset": 0, "now": "2019-08-24T14:15:22Z"}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.
Add case file POST
Names the person and, optionally, the audit entry the ban came from; otherwise the newest recorded ban of that person is used, or the ban list's row. Takes the profile snapshot from what Modbot has stored, then asks the profile sync for a fresher copy -- never the other way round, because the write-up must not wait on VRChat. One case file per ban: a second is refused with 409 naming the first. Recorded as a fact against your account. Needs the `Ban` permission.