# Read workspace usage events

The individual acts behind the usage numbers, newest first and paged: who did what, folded into a feature. Narrow with member (a userId from a summary row) and feature. Reach for it when a usage figure needs explaining — which records, which imports, which messages made up the count.

Access class: `workspace:admin`.

## Endpoint

`GET /v1/workspace/usage/events`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| body | query | null | No |
| params | query | object | No |
| query | query | object | No |

## Responses

### 200

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "events": [
      "string"
    ],
    "features": [
      "string"
    ],
    "nextCursor": "string",
    "page": 1.5,
    "pageSize": 1.5,
    "since": "string",
    "total": 1.5,
    "until": "string",
    "window": "string"
  }
}
```

### default

a refusal: `{"error": "<what a person needs to read>"}`. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.

Content type: `application/json`.

```json
{
  "error": "string"
}
```