Update an existing role binding by changing its assigned role.
Payload Requirements
role_id is required and replaces the currently assigned role.role_id is mutable. The binding identity, principal, resource,
and timestamps stay the same.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.
Most Arize AI endpoints require authentication. For those endpoints that require authentication, include your API key in the request header using the format
The unique identifier of the role binding. A universally unique identifier
"RW50aXR5OjEyMzQ1"
Body containing role binding update parameters.
A universally unique identifier
"RW50aXR5OjEyMzQ1"
A role binding object.
Unique identifier for the role binding.
A universally unique identifier
"RW50aXR5OjEyMzQ1"
A universally unique identifier
"RW50aXR5OjEyMzQ1"
Resource type for the binding. Only SPACE and PROJECT are supported for
single-binding CRUD. resource_id must encode the same resource type.
SPACE, PROJECT A universally unique identifier
"RW50aXR5OjEyMzQ1"
Timestamp when the binding was created.
Timestamp when the binding was last updated.