Download evidence
/api/evidence/{hash}Served with Content-Disposition: attachment, the content type Modbot determined from the bytes themselves, X-Content-Type-Options: nosniff and a sandbox CSP. Every request is written to the audit log against your account: as "Evidence downloaded" every time, or as "Evidence viewed" when the request says view=true, at most once per person per file every ten minutes. case names the case file the page was opened from. On a store that can presign and with direct delivery on, this redirects to a five-minute URL and the bucket serves the bytes; otherwise they stream through Modbot and are re-hashed on the way past. Range requests are answered where the backend supports them, because that is what makes video seeking work.
Needs the ViewEvidence permission.
An API key, made on Settings, API keys. Every key starts with mbk_.
In: header
Path Parameters
64 <= length <= 64Query Parameters
Response Body
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X GET "https://example.com/api/evidence/stringstringstringstringstringstringstringstringstringstringstri"Get evidence details GET
Everything about a piece of evidence except its bytes. It is the file's own record, so it says nothing about which case files hold it and reportId is null. Needs the `ViewEvidence` permission.
Destroy evidence POST
Refcounted: content addressing means two case files can hold one object, so the case files still holding these bytes are named back rather than having their evidence quietly removed. caseId is the case file it is being destroyed from, withdrawn or not: that case file lets go of it as part of the destroy, and only the others stop it. There is no undo — no backend Modbot supports could implement one — and what survives is the hash, the size, the type, who destroyed it and why. Recorded as a fact against your account. Needs the `DestroyEvidence` permission.