Create a role binding

curl --request POST \
  --url https://api.arize.com/v2/role-bindings \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "role_id": "Um9sZToxOmFCY0Q=",
  "user_id": "VXNlcjo0MjphQmNE",
  "resource_type": "SPACE",
  "resource_id": "U3BhY2U6MTpWNEth"
}
'

{
  "id": "Um9sZUJpbmRpbmc6MTphQmNE",
  "role_id": "Um9sZToxOmFCY0Q=",
  "user_id": "VXNlcjo0MjphQmNE",
  "resource_type": "SPACE",
  "resource_id": "U3BhY2U6MTpWNEth",
  "created_at": "2024-06-01T10:00:00Z",
  "updated_at": "2024-06-01T10:00:00Z"
}

Role Bindings

Create a role binding

Create a new role binding that assigns a role to a user on a resource.

Payload Requirements

role_id, user_id, resource_type, and resource_id are required.
resource_type must be SPACE or PROJECT.
resource_id must be a unique identifier for the selected resource_type.
Only one binding per user and resource is allowed. If the target user already has any binding on the resource, the request returns 409 Conflict.
System-managed fields (id, created_at, updated_at) are returned by the server and are rejected on input.

Valid example

{
  "role_id": "Um9sZToxOlY0S2E=",
  "user_id": "VXNlcjoxOmxQZzI=",
  "resource_type": "PROJECT",
  "resource_id": "TW9kZWw6MTpGdmxM"
}

Invalid example

{
  "role_id": "Um9sZToxOlY0S2E=",
  "user_id": "VXNlcjoxOmxQZzI=",
  "resource_type": "PROJECT",
  "resource_id": "U3BhY2U6MTp1Rk4x"
}

This fails because resource_id must encode a PROJECT ID when resource_type is PROJECT.

Use PATCH /v2/role-bindings/{binding_id} to change the assigned role for an existing binding.

This endpoint is in beta, read more here.

POST

role-bindings

Create a role binding

curl --request POST \
  --url https://api.arize.com/v2/role-bindings \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "role_id": "Um9sZToxOmFCY0Q=",
  "user_id": "VXNlcjo0MjphQmNE",
  "resource_type": "SPACE",
  "resource_id": "U3BhY2U6MTpWNEth"
}
'

{
  "id": "Um9sZUJpbmRpbmc6MTphQmNE",
  "role_id": "Um9sZToxOmFCY0Q=",
  "user_id": "VXNlcjo0MjphQmNE",
  "resource_type": "SPACE",
  "resource_id": "U3BhY2U6MTpWNEth",
  "created_at": "2024-06-01T10:00:00Z",
  "updated_at": "2024-06-01T10:00:00Z"
}

Authorizations

Authorization

string

header

required

Most Arize AI endpoints require authentication. For those endpoints that require authentication, include your API key in the request header using the format

Body

application/json

Body containing role binding creation parameters.

role_id

string

required

A universally unique identifier (base64-encoded opaque string).

Example:

"RW50aXR5OjEyMzQ1"

user_id

string

required

A universally unique identifier (base64-encoded opaque string).

Example:

"RW50aXR5OjEyMzQ1"

resource_type

enum<string>

required

Resource type for the binding. Only SPACE and PROJECT are supported for single-binding CRUD. resource_id must encode the same resource type.

Available options:

SPACE,

PROJECT

resource_id

string

required

A universally unique identifier (base64-encoded opaque string).

Example:

"RW50aXR5OjEyMzQ1"

Response

Role binding successfully created.

string

required

Unique identifier for the role binding.

role_id

string

required

A universally unique identifier (base64-encoded opaque string).

Example:

"RW50aXR5OjEyMzQ1"

user_id

string

required

A universally unique identifier (base64-encoded opaque string).

Example:

"RW50aXR5OjEyMzQ1"

resource_type

enum<string>

required

Resource type for the binding. Only SPACE and PROJECT are supported for single-binding CRUD. resource_id must encode the same resource type.

Available options:

SPACE,

PROJECT

resource_id

string

required

A universally unique identifier (base64-encoded opaque string).

Example:

"RW50aXR5OjEyMzQ1"

created_at

string<date-time>

required

Timestamp when the binding was created.

updated_at

string<date-time>

required

Timestamp when the binding was last updated.

List role bindings Get a role binding

⌘I