Update group role
Deprecated
/api/group/rolesChange a role: id names it. Leave name, description or permissions out to keep them; permissions is the whole list, which VRChat replaces. Only the fields that differ from what Modbot last recorded are sent. One request, never retried. Once VRChat accepts, the audit log records who changed it and each field's old and new value.
Needs the ManageGroupRoles permission.
Kept for older clients: use PUT /api/group/roles/{id}.
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
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X PUT "https://example.com/api/group/roles" \ -H "Content-Type: application/json" \ -d '{ "id": null, "name": null, "description": null, "permissions": null }'{ "role": { "id": "string", "name": null, "description": null, "permissions": [ "string" ], "order": 0, "isDefault": true, "isManagementRole": true, "isSelfAssignable": true, "requiresTwoFactor": true, "heldByModbot": true }}Create group role POST
Create a role in the group on VRChat. `name` is required; `description` and `permissions` (VRChat's ids) are optional. One request, never retried; a refusal answers with VRChat's own message, and a 403 for a permission Modbot's VRChat account lacks names it in `missingGroupPermission`. Once VRChat accepts, the audit log records who created it. Needs the `ManageGroupRoles` permission.
Delete group role POST
Delete a role on VRChat. `id` names it; `name` is kept in the audit log with the deletion, as the page showed it. Members who had the role lose it. One request, never retried. A role VRChat no longer has answers 404. Needs the `ManageGroupRoles` permission. Kept for older clients: use `DELETE /api/group/roles/{id}`.