---
title: "List the roles of each product"
description: "Each product's roles with their permissions on its API, and whether the caller may grant each product's roles.\n\n- **Scopes:** any one of `account:members:read`, `account:members:write`\n- **Credentials:** an API key, a client-credentials token or a person's access token\n- **Effect:** read-only; safe to retry\n- **Limits:** response up to 256 KB\n- **CLI:** `arbol account roles list` · **MCP tool:** `account_roles_list`"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.getarbol.com/llms.txt
> Use this file to discover all available pages before exploring further.

Path: Account API › Roles

`GET /v1/account/roles`

Each product's roles with their permissions on its API, and whether the caller may grant each product's roles.

- **Scopes:** any one of `account:members:read`, `account:members:write`
- **Credentials:** an API key, a client-credentials token or a person's access token
- **Effect:** read-only; safe to retry
- **Limits:** response up to 256 KB
- **CLI:** `arbol account roles list` · **MCP tool:** `account_roles_list`

## Authentication

Requires one of the following:

- `arbolHuman`, oauth2, scopes: `account:members:read`
- `arbolHuman`, oauth2, scopes: `account:members:write`
- `arbolMachine`, oauth2, scopes: `account:members:read`
- `arbolMachine`, oauth2, scopes: `account:members:write`
- `arbolApiKey`, http, header `Authorization`

## Query parameters

- `cursor` (`account.roles.list.query.cursor`; string, optional) — Opaque cursor returned by pageInfo; omit it to request the first page.
- `direction` (`account.roles.list.query.direction`; string, optional) — Direction to traverse the stable keyset ordering from the supplied cursor.
  - one of `"forward"`, `"backward"`; default `"forward"`
- `limit` (`account.roles.list.query.limit`; integer, optional) — Maximum items returned in one page. Defaults to 25; larger reads require another cursor.
  - min 1; max 100; default `25`

## Code samples

### cURL

```bash
curl https://api.getarbol.com/v1/account/roles \
  --header "Authorization: Bearer $ARBOL_API_KEY"
```

### TypeScript

```typescript
import { createClient } from "@arbol-ai/sdk";

const arbol = createClient({
  baseUrl: "https://api.getarbol.com",
  token: process.env.ARBOL_API_KEY!,
});

const { data } = await arbol.account.roles.list();
```

### Rust

```rust
use arbol_sdk::{types, Client, Credential};

let arbol = Client::new(Credential::ApiKey(std::env::var("ARBOL_API_KEY")?))?;

let data = arbol
    .account()
    .roles()
    .list(&types::AccountRolesListInput::default())
    .await?;
```

### CLI

```bash
arbol account roles list
```

### MCP

```json
{
  "name": "account_roles_list",
  "arguments": {}
}
```

## Responses

### 200

Successful operation.

#### Example

```json
{
  "success": true,
  "data": {
    "data": [
      {
        "id": "raiz",
        "assignable": true,
        "roles": [
          {
            "name": "string",
            "description": "string",
            "permissions": [
              "string"
            ]
          }
        ]
      }
    ],
    "object": "list",
    "pageInfo": {
      "hasNextPage": true,
      "hasPreviousPage": true,
      "nextCursor": "string",
      "previousCursor": "string"
    }
  },
  "error": null,
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.roles.list.response.200.success`; boolean, required)
  - one of `true`
- `data` (`account.roles.list.response.200.data`; object, required)
  - `data` (`account.roles.list.response.200.data.data`; array<object>, required) — Items admitted by this resource contract within the verified organization.
    - `id` (`account.roles.list.response.200.data.data.id`; string, required) — A product whose team Account administers: Raíz, Agenda, Ámbar or Account itself.
      - one of `"raiz"`, `"agenda"`, `"ambar"`, `"account"`
    - `assignable` (`account.roles.list.response.200.data.data.assignable`; boolean, required) — Whether the caller may grant this product's roles.
    - `roles` (`account.roles.list.response.200.data.data.roles`; array<object>, required)
      - `name` (`account.roles.list.response.200.data.data.roles.name`; string, required) — A role name, such as calendar:operator.
        - minLength 1; maxLength 128
      - `description` (`account.roles.list.response.200.data.data.roles.description`; string | null, required)
        - maxLength 1024
      - `permissions` (`account.roles.list.response.200.data.data.roles.permissions`; array | null, required) — The role's permissions on the product's API, which say what it may do there; null when the identity service did not answer.
  - `object` (`account.roles.list.response.200.data.object`; string, required) — Discriminator for a resource list response.
  - `pageInfo` (`account.roles.list.response.200.data.pageInfo`; object, required) — Opaque navigation cursors for this page’s stable keyset order.
    - `hasNextPage` (`account.roles.list.response.200.data.pageInfo.hasNextPage`; boolean, required) — Whether a later page exists in the current ordering.
    - `hasPreviousPage` (`account.roles.list.response.200.data.pageInfo.hasPreviousPage`; boolean, required) — Whether an earlier page exists in the current ordering.
    - `nextCursor` (`account.roles.list.response.200.data.pageInfo.nextCursor`; string | null, required) — Opaque cursor for the next page, or null when there is none.
    - `previousCursor` (`account.roles.list.response.200.data.pageInfo.previousCursor`; string | null, required) — Opaque cursor for the previous page, or null when there is none.
- `error` (`account.roles.list.response.200.error`; unknown, required)
- `metadata` (`account.roles.list.response.200.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.roles.list.response.200.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 400

`INVALID_INPUT`: The request does not match the published schema.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "INVALID_INPUT",
    "message": "string",
    "retryable": false,
    "data": {
      "issues": [
        {
          "path": "string",
          "message": "string"
        }
      ]
    }
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.roles.list.response.400.success`; boolean, required)
  - one of `false`
- `data` (`account.roles.list.response.400.data`; unknown, required)
- `error` (`account.roles.list.response.400.error`; object, required) — The request does not match the published schema.
  - `code` (`account.roles.list.response.400.error.code`; string, required) — The failure code, stable across releases.
    - one of `"INVALID_INPUT"`
  - `message` (`account.roles.list.response.400.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`account.roles.list.response.400.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`account.roles.list.response.400.error.data`; object, required)
    - `issues` (`account.roles.list.response.400.error.data.issues`; array<object>, optional)
      - `path` (`account.roles.list.response.400.error.data.issues.path`; string, required) — RFC 6901 JSON Pointer to the refused field; empty for the whole input.
        - maxLength 256
      - `message` (`account.roles.list.response.400.error.data.issues.message`; string, required)
        - maxLength 256
- `metadata` (`account.roles.list.response.400.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.roles.list.response.400.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 401

`UNAUTHORIZED`: A valid access token is required.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "UNAUTHORIZED",
    "message": "string",
    "retryable": false,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.roles.list.response.401.success`; boolean, required)
  - one of `false`
- `data` (`account.roles.list.response.401.data`; unknown, required)
- `error` (`account.roles.list.response.401.error`; object, required) — A valid access token is required.
  - `code` (`account.roles.list.response.401.error.code`; string, required) — The failure code, stable across releases.
    - one of `"UNAUTHORIZED"`
  - `message` (`account.roles.list.response.401.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`account.roles.list.response.401.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`account.roles.list.response.401.error.data`; object, required) — No fields.
- `metadata` (`account.roles.list.response.401.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.roles.list.response.401.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 403

`FORBIDDEN`: The token does not authorize this operation.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "FORBIDDEN",
    "message": "string",
    "retryable": false,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.roles.list.response.403.success`; boolean, required)
  - one of `false`
- `data` (`account.roles.list.response.403.data`; unknown, required)
- `error` (`account.roles.list.response.403.error`; object, required) — The token does not authorize this operation.
  - `code` (`account.roles.list.response.403.error.code`; string, required) — The failure code, stable across releases.
    - one of `"FORBIDDEN"`
  - `message` (`account.roles.list.response.403.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`account.roles.list.response.403.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`account.roles.list.response.403.error.data`; object, required) — No fields.
- `metadata` (`account.roles.list.response.403.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.roles.list.response.403.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 409

`IDENTITY_REJECTED`: The identity service refused the change.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "IDENTITY_REJECTED",
    "message": "string",
    "retryable": false,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.roles.list.response.409.success`; boolean, required)
  - one of `false`
- `data` (`account.roles.list.response.409.data`; unknown, required)
- `error` (`account.roles.list.response.409.error`; object, required) — The identity service refused the change.
  - `code` (`account.roles.list.response.409.error.code`; string, required) — The failure code, stable across releases.
    - one of `"IDENTITY_REJECTED"`
  - `message` (`account.roles.list.response.409.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`account.roles.list.response.409.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`account.roles.list.response.409.error.data`; object, required) — No fields.
- `metadata` (`account.roles.list.response.409.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.roles.list.response.409.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 429

`RATE_LIMITED`: The request rate limit was exceeded. Try again later.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "RATE_LIMITED",
    "message": "string",
    "retryable": true,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.roles.list.response.429.success`; boolean, required)
  - one of `false`
- `data` (`account.roles.list.response.429.data`; unknown, required)
- `error` (`account.roles.list.response.429.error`; object, required) — The request rate limit was exceeded. Try again later.
  - `code` (`account.roles.list.response.429.error.code`; string, required) — The failure code, stable across releases.
    - one of `"RATE_LIMITED"`
  - `message` (`account.roles.list.response.429.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`account.roles.list.response.429.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `true`
  - `data` (`account.roles.list.response.429.error.data`; object, required) — No fields.
- `metadata` (`account.roles.list.response.429.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.roles.list.response.429.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 500

`INTERNAL_ERROR`: The service could not complete the operation.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "INTERNAL_ERROR",
    "message": "string",
    "retryable": false,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.roles.list.response.500.success`; boolean, required)
  - one of `false`
- `data` (`account.roles.list.response.500.data`; unknown, required)
- `error` (`account.roles.list.response.500.error`; object, required) — The service could not complete the operation.
  - `code` (`account.roles.list.response.500.error.code`; string, required) — The failure code, stable across releases.
    - one of `"INTERNAL_ERROR"`
  - `message` (`account.roles.list.response.500.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`account.roles.list.response.500.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`account.roles.list.response.500.error.data`; object, required) — No fields.
- `metadata` (`account.roles.list.response.500.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.roles.list.response.500.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 502

`OUTCOME_UNKNOWN`: The operation may have been applied; check its result before repeating it.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "OUTCOME_UNKNOWN",
    "message": "string",
    "retryable": false,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.roles.list.response.502.success`; boolean, required)
  - one of `false`
- `data` (`account.roles.list.response.502.data`; unknown, required)
- `error` (`account.roles.list.response.502.error`; object, required) — The operation may have been applied; check its result before repeating it.
  - `code` (`account.roles.list.response.502.error.code`; string, required) — The failure code, stable across releases.
    - one of `"OUTCOME_UNKNOWN"`
  - `message` (`account.roles.list.response.502.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`account.roles.list.response.502.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`account.roles.list.response.502.error.data`; object, required) — No fields.
- `metadata` (`account.roles.list.response.502.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.roles.list.response.502.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 503

- `UPSTREAM_UNAVAILABLE`: The upstream service could not complete the request.
- `ACCOUNT_NOT_CONFIGURED`: Account administration is not configured yet.
- `IDENTITY_UNAVAILABLE`: The identity service did not answer.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "UPSTREAM_UNAVAILABLE",
    "message": "string",
    "retryable": true,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.roles.list.response.503.success`; boolean, required)
  - one of `false`
- `data` (`account.roles.list.response.503.data`; unknown, required)
- `error` (`account.roles.list.response.503.error`; one of, required)
  - one of: `UpstreamUnavailableFailure`, `AccountAccountNotConfiguredFailure`, `AccountIdentityUnavailableFailure`
  - discriminator: `code`
- `metadata` (`account.roles.list.response.503.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.roles.list.response.503.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 504

`UPSTREAM_TIMEOUT`: The upstream service did not respond before its deadline.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "UPSTREAM_TIMEOUT",
    "message": "string",
    "retryable": true,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`account.roles.list.response.504.success`; boolean, required)
  - one of `false`
- `data` (`account.roles.list.response.504.data`; unknown, required)
- `error` (`account.roles.list.response.504.error`; object, required) — The upstream service did not respond before its deadline.
  - `code` (`account.roles.list.response.504.error.code`; string, required) — The failure code, stable across releases.
    - one of `"UPSTREAM_TIMEOUT"`
  - `message` (`account.roles.list.response.504.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`account.roles.list.response.504.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `true`
  - `data` (`account.roles.list.response.504.error.data`; object, required) — No fields.
- `metadata` (`account.roles.list.response.504.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`account.roles.list.response.504.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.


Source: https://docs.getarbol.com/api/account/roles/list/index.md