curl --request POST \
  --url https://api.arize.com/v2/spaces/{space_id}/users \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "user_id": "VXNlcjoxMjM0NQ==",
  "role": {
    "type": "PREDEFINED",
    "name": "MEMBER"
  }
}
'

{
  "id": "U3BhY2VNZW1iZXI6MQ==",
  "user_id": "VXNlcjoxMjM0NQ==",
  "space_id": "U3BhY2U6MQ==",
  "role": {
    "type": "PREDEFINED",
    "name": "MEMBER"
  }
}

Spaces

Add a user to a space

Add a single existing account user to a space with a specified role.

Payload Requirements

user_id is required and must be a valid user identifier (base64).
role is required and must be a role assignment object with a type discriminator:
- { "type": "PREDEFINED", "name": "ADMIN" } — one of the predefined roles: ADMIN, MEMBER, READ_ONLY, ANNOTATOR.
- { "type": "CUSTOM", "id": "<role_id>" } — a custom RBAC role, using its unique identifier.
If the user is already a member, their role is updated to the specified value (upsert).
The user must already be a member of the space’s parent organization; auto-enrollment is not performed (400 if not a member).

Role constraints

Users with an annotator account role can only be assigned the annotator predefined space role.
Users with a non-annotator account role cannot be assigned the annotator predefined space role.

Authorization Requires space admin role when using a PREDEFINED role, or ROLE_BINDING_CREATE permission (RBAC) when using a CUSTOM role.

This endpoint is in beta, read more here.

POST

spaces

{space_id}

users

curl --request POST \
  --url https://api.arize.com/v2/spaces/{space_id}/users \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "user_id": "VXNlcjoxMjM0NQ==",
  "role": {
    "type": "PREDEFINED",
    "name": "MEMBER"
  }
}
'

{
  "id": "U3BhY2VNZW1iZXI6MQ==",
  "user_id": "VXNlcjoxMjM0NQ==",
  "space_id": "U3BhY2U6MQ==",
  "role": {
    "type": "PREDEFINED",
    "name": "MEMBER"
  }
}

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

Path Parameters

space_id

string

required

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

Example:

"RW50aXR5OjEyMzQ1"

Body

application/json

Body containing the user to add to the space

user_id

string

required

The unique identifier of the user to add

Example:

"RW50aXR5OjEyMzQ1"

role

object

required

Strict request form of SpaceRoleAssignment. Used in write request bodies.

PREDEFINED: { "type": "PREDEFINED", "name": "ADMIN" | "MEMBER" | "READ_ONLY" | "ANNOTATOR" }
CUSTOM: { "type": "CUSTOM", "id": "<encoded-role-id>" }

Option 1
Option 2

Show child attributes

Response

User successfully added to the space

A space membership record.

string

required

Unique identifier for the membership record

Example:

"RW50aXR5OjEyMzQ1"

user_id

string

required

The unique identifier of the user

Example:

"RW50aXR5OjEyMzQ1"

space_id

string

required

The unique identifier of the space

Example:

"RW50aXR5OjEyMzQ1"

role

object

required

Specifies which role to assign within a space. Discriminated by type:

PREDEFINED: a built-in platform role — { "type": "PREDEFINED", "name": "ADMIN" | "MEMBER" | "READ_ONLY" | "ANNOTATOR" }
CUSTOM: a custom RBAC role identified by its ID — { "type": "CUSTOM", "id": "<encoded-role-id>" }

Used wherever a space-level role assignment is required (memberships, service key bindings, etc.).

Option 1
Option 2

Show child attributes

⌘I

API reference

API clients

Add a user to a space

Authorizations

Path Parameters

Body

Response