# Get Cloudflare analytics dashboard

> GET /api/services/cloudflare/analytics/dashboard on the Vigilbase One API.

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

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

## 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)
- `range` (string)
- `variant` (string)
- `zoneId` (string)

## Body (application/json)

Validation schema (Zod source):

```ts
QuerySchema = z.object({
  customerId: z.string().uuid('Invalid customer ID format'),
  zoneId: z.string().regex(CLOUDFLARE_ID, 'Invalid zone ID format').optional(),
  accountId: z.string().regex(CLOUDFLARE_ID, 'Invalid account ID format').optional(),
  range: z.enum(TRAFFIC_RANGES).default('24h'),
  variant: z.enum(['shield', 'enterprise']).optional(),
})
```

## 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/analytics/dashboard' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{}'
```