Update a role binding
Update an existing role binding by changing its assigned role.
Payload Requirements
role_idis required and replaces the currently assigned role.- Only
role_idis 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.
Authorizations
Most Arize AI endpoints require authentication. For those endpoints that require authentication, include your API key in the request header using the format
Path Parameters
The unique role binding identifier (base64) A universally unique identifier (base64-encoded opaque string).
"RW50aXR5OjEyMzQ1"
Body
Body containing role binding update parameters.
A universally unique identifier (base64-encoded opaque string).
"RW50aXR5OjEyMzQ1"
Response
A role binding object.
Unique identifier for the role binding.
A universally unique identifier (base64-encoded opaque string).
"RW50aXR5OjEyMzQ1"
A universally unique identifier (base64-encoded opaque string).
"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 (base64-encoded opaque string).
"RW50aXR5OjEyMzQ1"
Timestamp when the binding was created.
Timestamp when the binding was last updated.