Get data settings
/api/settings/dataRetention, measured storage, and what this deployment is running on. capacityBytes is an optional what-if input. It is not stored: nothing in Modbot behaves differently for having been told, so it is answered against rather than persisted.
An API key, made on Settings, API keys. Every key starts with mbk_.
In: header
Query Parameters
int64Response Body
application/json
application/problem+json
application/problem+json
curl -X GET "https://example.com/api/settings/data"{ "retention": { "moderationFactRetentionDays": 0, "presenceFactRetentionDays": 0, "discordMessageRetentionDays": 0, "memberReportRetentionDays": null }, "storage": { "bytes": 0, "facts": 0, "bytesPerFact": 0.1, "factsPerDay": 0.1, "observedDays": 0.1, "confidence": "string", "bytesPerDay": 0.1, "capacityExhausted": null, "measuredAt": "2019-08-24T14:15:22Z", "history": [ { "day": "2019-08-24", "bytes": 0 } ] }, "deployment": { "version": "string", "commit": null, "branch": null, "platform": "string", "platformEvidence": null, "logFilesWritten": true }}Update the new staff checklist PUT
Replace both lists and the reminder channel. Blank lines are dropped, and an empty channel turns the reminders off. A trial already started keeps the lines it was given; the change reaches trials started after it. Needs the `ManageUsers` permission.
Set retention PUT
Zero means keep forever, which is the default for both classes. Turning a window on schedules destruction of data that cannot be recovered or filled in later.