Reorder ban reasons
/api/settings/ban-reasons/orderPut the reasons in this order.
Needs the EditClassifications permission.
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/ban-reasons/order" \ -H "Content-Type: application/json" \ -d '{ "ids": [ "6e0346a3-e54d-40e3-9779-4ba1e707e35b" ] }'{ "reasons": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "label": "string", "description": "string", "sortOrder": 0, "isActive": true, "needsWrittenReason": true, "usedFor": [ "string" ] } ], "canEdit": true, "reasonAlwaysRequired": true}Require a reason on every action PUT
Whether a kick, an unban and turning a join request down each need a reason, as a ban always does (foundation 5.8.1: optional unless the group asks for it). Approving a join request never takes one. Needs the `EditClassifications` permission.
Update ban reason PUT
Reword a reason, change which actions offer it, or switch it on or off. There is no delete: case files cite reasons by id, and one that pointed at a reason nobody can name any more would have lost its classification. Switch it off instead; it stays on the case files that picked it and leaves the buttons. Needs the `EditClassifications` permission.