# Get account

> Customer-facing account overview for Vigilbase One (CLI + dashboard clients).

Source: https://docs.vigilbase.com/one/api/reference/account/get-account

`GET https://one.vigilbase.com/api/account`

Customer-facing account overview for Vigilbase One (CLI + dashboard clients). Accepts session cookies or device-auth Bearer tokens. User/org come from the session; customer summary requires read:customers (or partner equivalent).

## 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:customers`, `read:partner_customers`

## 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/account' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN"
```

With the Vigilbase CLI:

```bash
vigilbase account
```

See also the [guide](https://docs.vigilbase.com/one/api/account-and-billing).