Modbot Docs
APIAPI referenceEvidence

Send the bytes

PUT/api/evidence/uploads/{uploadId}

Phase 2: send the bytes, as a raw body. The body is the file and nothing else — no form encoding. The cap is enforced against bytes actually seen rather than against Content-Length, because Content-Length is a claim and a chunked body makes none. Retrying the same upload id overwrites its staging object rather than accumulating a second one.

Needs the UploadEvidence permission.

AuthorizationBearer <token>

An API key, made on Settings, API keys. Every key starts with mbk_.

In: header

Path Parameters

uploadId*string

Response Body

application/json

application/problem+json

application/problem+json

application/problem+json

application/problem+json

application/problem+json

curl -X PUT "https://example.com/api/evidence/uploads/string"
{  "hash": "string",  "byteSize": 0}

Modbot is not endorsed by or affiliated with VRChat Inc. or Discord Inc. VRChat is a trademark of VRChat Inc. Discord is a trademark of Discord Inc. SteamVR is a trademark of Valve Corporation. Windows is a trademark of Microsoft Corporation. Docker is a trademark of Docker, Inc. PostgreSQL is a trademark of the PostgreSQL Community Association of Canada. Railway is a trademark of Railway Corp. Other names are trademarks of their respective owners; see Legal. Modbot and its logo are trademarks of the Modbot project. Open source under AGPL-3.0.

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.

Finish the upload POST

Phase 3: hash it, decide what it is, and attach it. Modbot reads the staged bytes back, hashes them, decides the content type from the bytes themselves — never from the filename and never from what the client claimed — checks the size that was actually stored against the per-file limit and the per-case-file and whole-install totals, promotes the object to its content-addressed key, writes the metadata and puts the file on the case file. SVG and HTML are refused outright. Idempotent on the upload id. reportId names the case file to attach to when the upload was begun without one, so a file can be sent before its case file is written; naming a different case file from the one the upload was begun for is refused with 409. The case file must exist (404), must not be withdrawn (409), and must be the caller's own or the caller must be allowed to ban (403); with no case file at all the commit is refused with 400. clipId names a saved clip from the case file's clips list: the file must hash to what that moderator's companion reported when the clip was saved (409 when it does not, 404 when there is no such clip), and is then kept as captured, with where and when it was saved. Recorded as a fact against your account. Needs the `UploadEvidence` permission.