Set evidence limits
/api/settings/evidence/limitsPer-file, per-report and per-deployment caps, and direct delivery. No round trip: none of these repoints a store. Zero means no limit on the two totals; the per-file cap is enforced three times and cannot be zero.
An API key, made on Settings, API keys. Every key starts with mbk_.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
curl -X PUT "https://example.com/api/settings/evidence/limits" \ -H "Content-Type: application/json" \ -d '{ "maxFileBytes": 0, "maxReportBytes": 0, "maxDeploymentBytes": 0 }'{ "maxFileBytes": 0, "maxReportBytes": 0, "maxDeploymentBytes": 0}Set evidence backend PUT
The round trip runs first and the row changes only if it passed, so a backend that cannot store evidence cannot be selected. Choosing the filesystem backend on a directory Modbot cannot prove survives a restart returns requiresAcknowledgement with the warning to show; echo that text back in acknowledgeWarning to proceed, and it is recorded verbatim against your name. Switching backends while objects are stored is refused: changing the setting does not move them.
Check the store marker POST
The same three-valued probe startup takes. A store that answers with somebody else's store marker, or with none, locks; a store that does not answer at all does not, because silence is not evidence of loss.