Get evidence details
/api/evidence/{hash}/metadataEverything 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.
An API key, made on Settings, API keys. Every key starts with mbk_.
In: header
Path Parameters
64 <= length <= 64Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
curl -X GET "https://example.com/api/evidence/stringstringstringstringstringstringstringstringstringstringstri/metadata"{ "hash": "string", "byteSize": 0, "contentType": "string", "fileName": null, "uploaderId": null, "reportId": null, "origin": "string", "firstStoredAt": "2019-08-24T14:15:22Z", "destroyed": true, "destroyedAt": null, "destroyedBy": null, "destroyedReason": null, "attachedAt": null, "takenOffAt": null, "takenOffBy": null, "clip": null}List evidence GET
What is on a case file, or on any case file. Answered entirely from the database, so listing evidence costs the store no request and no egress. Destroyed items are listed too, because a case file that looks like it never had evidence is indistinguishable from one nobody ever documented. A file taken off a case file is left out unless includeTakenOff is true. One file on two case files is listed once for each. Returns at most 500 items, newest first. Needs the `ViewEvidence` permission.
Download evidence GET
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.