Source: https://datafa.st/docs/api/account/websites/list
Markdown source: https://datafa.st/docs/api/account/websites/list.md
Description: List websites available to the token.

# List websites

`GET https://datafa.st/api/v1/admin/websites`

List all websites the token can access, including your role on each (`owner`, `member`, or `viewer`). Scoped tokens only return websites in their allowlist.

Use the returned `_id` as `websiteId` when calling Website API endpoints with a `dft_` token.

## Request

This endpoint does not require any path, query, or body parameters.

## Response

Returns a JSON object with `status: "success"` and endpoint-specific fields in `data`.

#### Response fields

| Field | Type | Description |
| --- | --- | --- |
| `data[]._id` | string | Website ObjectId. |
| `data[].domain` | string | Website domain. |
| `data[].name` | string\|null | Human-readable name for the resource or event. The exact meaning depends on the endpoint. |
| `data[].trackingId` | string | Script tracking ID used in `data-website-id`. |
| `data[].timezone` | string | Timezone used to interpret dates and group analytics buckets. Defaults to the website timezone. |
| `data[].currency` | string | Currency code for money values, such as `USD` or `EUR`. |
| `data[].role` | string | Caller role on the website: `owner`, `member`, or `viewer`. |

### Authentication

Use a `dft_` account token with `websites:read`.

### Errors

See [API errors](/docs/api#errors) for the standard error envelope, auth failures, validation errors, permission errors, and rate limits.

## Code examples

### Example request

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

### Success response

```json
{
  "status": "success",
  "data": [{
    "_id": "665f0b3c4d2e1a0012345678",
    "domain": "example.com",
    "name": "Example",
    "trackingId": "dfid_abc123",
    "timezone": "America/New_York",
    "currency": "USD",
    "role": "owner"
  }]
}
```