Set evidence backend
/api/settings/evidence/backendThe 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.
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
curl -X PUT "https://example.com/api/settings/evidence/backend" \ -H "Content-Type: application/json" \ -d '{ "backend": "string" }'{ "succeeded": true, "failedStep": null, "message": "string", "storeId": null, "requiresAcknowledgement": true, "durability": null}Test evidence store POST
Writes a test file, reads it back, compares the bytes, promotes it to its content-addressed key, reads it again, deletes it, and writes the store store marker. Nothing is persisted. Leave secretAccessKey empty to test with the credential already on file.
Set evidence limits PUT
Per-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.