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
}
共享用户与角色
更新自定义角色
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
}
在 Management API 主机（
同时支持
api.scanova.io）上更新账户自己的某个自定义角色，使用您的原始 Management API 密钥进行身份验证。
PUT https://api.scanova.io/multi-users/access-levels/{pk}/
PATCH https://api.scanova.io/multi-users/access-levels/{pk}/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
integer
必填
角色的
id。PUT（完整替换）和 PATCH（部分更新），二者接受与创建自定义角色中记录相同的 name/permissions 字段。
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
}
系统角色无法在此编辑
只有账户自己的自定义角色（is_custom: true）可通过此端点写入——属于系统角色（或其他账户自定义角色）的 pk 会返回 404，与完全不存在的角色返回结果相同。
相关内容
- 获取角色——更新前先查看该角色。
- 创建自定义角色——此更新复用的字段参考。
- 删除自定义角色——将该角色彻底删除。
- Management API 概览——适用于此端点的身份验证方案和配额规则。
授权
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.
路径参数
响应
Role updated.
此页面对您有帮助吗？