Take evidence off a case file
/api/cases/{id}/evidence/{hash}/take-offEnds this case file's hold on the file and keeps a line saying it was there. The bytes stay, and so does every other case file's hold on them; putting the file back is attaching it again. For the author of the case file or anyone who may ban, while it is not withdrawn (409 once it is). Recorded as a fact against your account. 404 when the file is not on this case file.
Needs the UploadEvidence permission.
An API key, made on Settings, API keys. Every key starts with mbk_.
In: header
Path Parameters
uuid64 <= length <= 64Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://example.com/api/cases/497f6eca-6276-4993-bfeb-53cbbbba6f08/evidence/stringstringstringstringstringstringstringstringstringstringstri/take-off"{ "caseId": "string", "hash": "string"}Capture profile again POST
Allowed once per case file, and only when VRChat has answered with a newer profile since the snapshot was taken. The snapshot it replaces is kept in full in the fact that records this, so the first capture is never lost.
Start an upload POST
Phase 1: reserve an upload and find out where the bytes go. Returns the cap in force, the accepted formats so the client can filter before a byte moves, and a target. On a store that can be written to directly the target is a presigned PUT straight to the bucket; otherwise it is Modbot's own transfer endpoint. That is a capability difference, not a failure. Needs the `UploadEvidence` permission.