Skip to main content
The RBAC REST API gives you programmatic control over users, roles, role bindings, and resource restrictions, the same access settings you manage in the Arize AX UI. Use it to script onboarding and offboarding or to audit who has access to what. Requests are authenticated with an API key or service key sent as a bearer token:

Users and membership

POST /v2/users accepts the account roles ADMIN, MEMBER, and ANNOTATOR. It cannot create an Account Member - UI Only user. invite_mode takes one of these values: An identical EMAIL_LINK request for a pending invitation returns 200 and does not create a second invitation. Inactive users cannot be reinvited. NONE creates a verified user and sends no email. It returns 400 when the account enforces SSO. Invites and resends cap the account role at your own. See who can invite whom. PATCH /v2/users/{user_id} accepts a developer access override. Removing organization membership also removes the user from all of that organization’s spaces.

Roles

Custom role permissions use the form {RESOURCE}_{ACTION}, such as DATASET_CREATE. An update to permissions replaces the existing list, so the request must include every permission the role should keep. Predefined roles cannot be deleted, and a custom role cannot be deleted while it has role bindings. PATCH on a managed role returns 403. Deletes are soft. GET /v2/roles?is_predefined=true lists the managed roles with their permissions arrays, which enumerate every permission string.

Role bindings

resource_type accepts SPACE or PROJECT. A user has one binding per resource, and a duplicate returns 409. Only role_id can be updated on a binding, so changing the user or resource requires a new binding.

Resource restrictions

POST /v2/resource-restrictions takes only resource_id and infers PROJECT or DASHBOARD from it. POST /v2/role-bindings does not accept dashboards, so a restricted dashboard is open only to space, organization, and account admins. The restriction list is filtered to what the caller can manage after each page is read, so a page can be empty while has_more is still true. Paging ends when has_more is false.