curl -X PATCH "https://api.scanova.io/multi-users/access-levels/42/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{ "permissions": [23, 24, 31, 40] }'
{
"id": 42,
"name": "Regional Support",
"slug": null,
"permissions": [
{ "id": 23, "code": "QR_CODE_CAN_VIEW", "name": "Can view QR Code", "description": "Allows viewing QR code details.", "is_boolean": true }
],
"is_custom": true
}
Shared Users & Roles
Update a custom role
PATCH /multi-users/access-levels//
PATCH
/
multi-users
/
access-levels
/
{pk}
/
curl -X PATCH "https://api.scanova.io/multi-users/access-levels/42/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{ "permissions": [23, 24, 31, 40] }'
{
"id": 42,
"name": "Regional Support",
"slug": null,
"permissions": [
{ "id": 23, "code": "QR_CODE_CAN_VIEW", "name": "Can view QR Code", "description": "Allows viewing QR code details.", "is_boolean": true }
],
"is_custom": true
}
Updates one of the account’s own custom roles on the Management API host (
Both
api.scanova.io), authenticated with your raw Management API key.
PUT https://api.scanova.io/multi-users/access-levels/{pk}/
PATCH https://api.scanova.io/multi-users/access-levels/{pk}/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
integer
required
The role’s
id.PUT and PATCH are supported (PUT for a full replace, PATCH for a partial update) and accept the same name/permissions fields documented for Create a custom role.
curl -X PATCH "https://api.scanova.io/multi-users/access-levels/42/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{ "permissions": [23, 24, 31, 40] }'
{
"id": 42,
"name": "Regional Support",
"slug": null,
"permissions": [
{ "id": 23, "code": "QR_CODE_CAN_VIEW", "name": "Can view QR Code", "description": "Allows viewing QR code details.", "is_boolean": true }
],
"is_custom": true
}
System roles can’t be edited here
Only the account’s own custom roles (is_custom: true) are writable through this endpoint — a pk belonging to a system role (or another account’s custom role) returns 404, the same as one that doesn’t exist at all.
Related
- Retrieve a role — see the role before updating it.
- Create a custom role — the field reference this update reuses.
- Delete a custom role — remove this role entirely.
- Management API overview — the auth scheme and quota rules that apply to this endpoint.
Authorizations
Send your Management API key as the raw value of the Authorization header — no "Bearer " or "Token " prefix, and no other characters. Example: Authorization: 401f7ac837da42b97f613d789819ff93537bee6a. A header containing more than one space-separated part is rejected outright. Requests also require the request's Host header to be the management API host (e.g. api.scanova.io) — the same key sent to the regular API host will not authenticate.
Path Parameters
Response
Role updated.
Was this page helpful?