Update Role
Update a role's name, description and permission matrix. This is a full replacement of the matrix: the permissions you send become the role's complete set, and any resource you omit is reset to no access. To make a single change, send the role's current matrix with the one edit applied.
Changes take effect for every member assigned this role.
Permission required
Requires roles:update. The account owner always passes — the owner holds every permission implicitly.
Path parameters
uuid of the role to update (from /account/roles). Must belong to your active account.Deprecated: the legacy integer id is still accepted in the path until the sunset, answered with Deprecation and Sunset headers. Use the uuid.
Request body
{ "resource", "can_read", "can_write", "can_update", "can_delete" }. The verbs are read, write (= create), update and delete. Valid resource keys: endpoints, domains, certs, ips, firewall, rate_limits, traffic_inspector, members, roles, settings, billing. Unknown or duplicate keys are rejected; omitted resources are reset to no access.Response (200 OK)
Returns the updated role under role (uuid, account_uuid, …) with its new permissions matrix (each row carries role_uuid).
Deprecated: until the sunset this response also carries the legacy integer id and *_id fields. Don't use them; read uuid and the *_uuid fields.
Errors
name, an unknown / duplicate resource key, or an integer id after the sunset (integer_id_unsupported).roles:update.