Update a role binding
Changed onUpdate an existing role binding by changing its assigned role.
Payload Requirements
- role_id is required and replaces the currently assigned role.
- Only role_id is mutable. The binding identity, principal, resource, and timestamps stay the same.
- System-managed fields (id, user_id, resource_type, resource_id, created_at, updated_at) are not accepted in the request body.
Valid example
{
"role_id": "Um9sZToyOmRLMjQ="
}
Invalid example
{
"role_id": "Um9sZToyOmRLMjQ=",
"user_id": "VXNlcjoxOmxQZzI="
}
This fails because only role_id can be updated on an existing binding.
Authorization Requires both ROLE_BINDING_CREATE and ROLE_BINDING_DELETE permissions on the binding's resource. Together, these permissions grant administrator-level authority on the resource. If the binding does not exist, belongs to another account, or the caller lacks either permission, the endpoint returns 404.
Request
- Base URLhttps://api.arize.com
- URLhttps://api.arize.com/v2/role-bindings/{binding_id}
- AuthHTTP bearer
Path parameters
A universally unique identifier (base64-encoded opaque string).
The unique role binding identifier (base64)
Request body
Example request
{
"role_id": "RW50aXR5OjEyMzQ1"
}Response
A role binding object.
Example response
{
"role_id": "RW50aXR5OjEyMzQ1",
"user_id": "RW50aXR5OjEyMzQ1",
"resource_id": "RW50aXR5OjEyMzQ1"
}Changes
- breaking
the
response's property type changed fromstringto no type for status - info
added to the
response propertyallOflist for the response status
- breaking
- info
api operation id
role_bindings_updateremoved and replaced withupdate_role_binding - info
added the non-success response with the status
- info