Source: https://datafa.st/docs/api/account/access-tokens/list
Markdown source: https://datafa.st/docs/api/account/access-tokens/list.md
Description: List dft_ account tokens.

# List access tokens

`GET https://datafa.st/api/v1/admin/access-tokens`

List dft_ account tokens.

## Request

### Authentication

- `dft_` account token with `api-keys:read`.



## Response

Returns a JSON object with `status` and endpoint-specific fields.

### Response fields

| Field | Type | Description |
| --- | --- | --- |
| `data[]._id` | string | Token ObjectId. |
| `data[].name` | string|null | Human-readable name for the resource or event. The exact meaning depends on the endpoint. |
| `data[].displayKey` | string | Masked token shown in the dashboard. |
| `data[].scope` | string | Token scope. Account tokens use `user`. |
| `data[].permissions` | string[] | Granted permissions, or [`*`] for full access. |
| `data[].websiteIds` | string[] | Allowed website IDs. Empty means all websites available to the account. |
| `data[].lastUsedAt` | string|null | Last usage timestamp. |
| `data[].createdAt` | string | Creation timestamp. |
| `data[].key` | string | Only returned when creating a token. Full raw token shown once. |

### Errors

Common errors include `400` for invalid input, `401` for missing or invalid tokens, `403` for missing permissions or website access, `404` for missing resources, and `500` for server errors.

## Code examples

### Example request

```bash
curl -X GET "https://datafa.st/api/v1/admin/access-tokens" \
  -H "Authorization: Bearer dft_xxx"
```

### Success response

```json
{
  "status": "success",
  "data": [{
    "_id": "665f0b3c4d2e1a0012345678",
    "name": "Read only",
    "displayKey": "dft_ab1...xyz9",
    "scope": "user",
    "permissions": ["analytics:read", "websites:read"],
    "websiteIds": ["665f0b3c4d2e1a0012345678"],
    "lastUsedAt": null,
    "createdAt": "2026-05-21T00:00:00.000Z"
  }]
}
```