List unwritten case files
/api/cases/missingBans in the last N days with no case file, newest first. Read from the recorded ban facts, so it covers the window Modbot's audit-log sync covers and nothing before it. A ban is covered when a case file that stands names its audit entry, or was written for the same person on or after it. A withdrawn case file covers nothing. This is the list the accountability "bans without a report" signal reads.
Needs the ViewProfile permission.
An API key, made on Settings, API keys. Every key starts with mbk_.
In: header
Query Parameters
int32int32Response Body
application/json
application/problem+json
application/problem+json
curl -X GET "https://example.com/api/cases/missing"{ "bans": [ { "userId": "string", "displayName": null, "bannedAt": "2019-08-24T14:15:22Z", "bannedBefore": null, "auditEntryId": null, "factId": 0, "bannedBy": null, "liftedAt": null } ], "total": 0, "days": 0, "since": "2019-08-24T14:15:22Z", "now": "2019-08-24T14:15:22Z"}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.
Get evidence upload limits GET
Whether uploads are open right now, the formats accepted and the size limit per file -- the same `evidenceDelivery` a case file carries, for a screen that attaches files before the case file exists. The ban dialog uses it: files are sent as soon as they are picked and committed to the case file the ban writes. Needs the `ViewProfile` permission.