# List Cloudflare users

> Cloudflare's add-member API takes role IDs, while the invite dialog offers role names.

Source: https://docs.vigilbase.com/one/api/reference/services/get-services-cloudflare-users

`GET https://one.vigilbase.com/api/services/cloudflare/users`

Cloudflare's add-member API takes role IDs, while the invite dialog offers role names. Every requested role, by name or ID, is resolved against the account's own role list.

## Authorizations

Send one of these:

- `Authorization` (string, header, required): Bearer access token from Vigilbase Identity (`auth.vigilbase.com`), sent as `Authorization: Bearer <token>`. The CLI gets one with `vigilbase login`.
- `Authorization` (string, header, required): Organisation API key (`vb_one_…`) from **Settings → API keys** in Vigilbase One, sent as `Authorization: Bearer vb_one_…`. Read-only keys work. See [organisation API keys](https://docs.vigilbase.com/one/api#organisation-api-keys).
- Permissions checked: `read:services`

## Query parameters

- `accountId` (string)
- `customerId` (string)

## Responses

### 200

Success

### 401

Authentication required

### 403

Not permitted

## Example request

```bash
# Token from `vigilbase login`, or an API key (vb_one_…)
curl --request GET \
  --url 'https://one.vigilbase.com/api/services/cloudflare/users' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN"
```