Test evidence store
/api/settings/evidence/testWrites 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.
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 POST "https://example.com/api/settings/evidence/test" \ -H "Content-Type: application/json" \ -d '{ "backend": "string" }'{ "succeeded": true, "failedStep": null, "message": "string", "storeId": null, "requiresAcknowledgement": true, "durability": null}Get evidence settings GET
The configured evidence backend, its health, and what it is holding. Counts and bytes come from the blob record rather than from listing the store, because LIST is slow everywhere and billed on some providers. The S3 secret is never returned; secretStored says only whether one is on file.
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.