Show what a restore would change
/api/discord/snapshots/{id}/restore-previewWorks out, from the server as it is now, exactly what putting one role's or one channel's permissions back from the snapshot would change. Changes nothing.
Needs the ManageSettings permission.
An API key, made on Settings, API keys. Every key starts with mbk_.
In: header
Path Parameters
uuidRequest 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
application/problem+json
application/problem+json
curl -X POST "https://example.com/api/discord/snapshots/497f6eca-6276-4993-bfeb-53cbbbba6f08/restore-preview" \ -H "Content-Type: application/json" \ -d '{ "kind": "string", "targetId": "string", "fingerprint": null }'{ "kind": "string", "targetId": "string", "name": "string", "lines": [ "string" ], "problem": null, "missingPermission": true, "nothingToChange": true, "fingerprint": "string"}Compare two snapshots GET
What changed in roles and channels from the snapshot `from` to the snapshot `to`, or to the server as it is now when `to` is `now`. Roles and channels are told apart by their Discord id, so a rename shows as a change. Needs the `ViewAnalytics` permission.
Put a role's or a channel's permissions back POST
Puts one role's server-wide permissions, or one channel's permissions for roles, back to what the snapshot has. Needs Restore turned on in Settings, the bot connected and Manage Roles. The body carries the fingerprint from the preview; if the server no longer gives the same change the answer is 409. Settings for single members in a channel are left alone. Recorded in the audit log. Needs the `ManageSettings` permission.