List ban reasons
/api/settings/ban-reasonsThe reasons a moderator picks from when banning, kicking, unbanning or turning a join request down; usedFor says which actions offer each one. In button order, switched-off ones included with isActive false. Seeded with a plain default set the first time anybody asks, so the first case file can be written without inventing a list first. reasonAlwaysRequired says whether the actions other than a ban need a reason too.
An API key, made on Settings, API keys. Every key starts with mbk_.
In: header
Response Body
application/json
application/problem+json
curl -X GET "https://example.com/api/settings/ban-reasons"{ "reasons": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "label": "string", "description": "string", "sortOrder": 0, "isActive": true, "needsWrittenReason": true, "usedFor": [ "string" ] } ], "canEdit": true, "reasonAlwaysRequired": true}Check the store marker POST
The same three-valued probe startup takes. A store that answers with somebody else's store marker, or with none, locks; a store that does not answer at all does not, because silence is not evidence of loss.
Add ban reason POST
Add a reason to the end of the list. Needs the `EditClassifications` permission.