Source: https://datafa.st/docs/api/account/team/list
Markdown source: https://datafa.st/docs/api/account/team/list.md
Description: List team members.

# List team members

`GET https://datafa.st/api/v1/admin/websites/{websiteId}/team`

List team members.

## Request

### Authentication

- `dft_` account token with `team:read`.


### Path parameters

| Parameter | Type | Description |
| --- | --- | --- |
| `websiteId` | string | Website ObjectId used by account tokens to choose which website to query or manage. Website ObjectId. The caller token must have access to this website. |

## Response

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

### Response fields

| Field | Type | Description |
| --- | --- | --- |
| `data[].userId` | string | Team member user ObjectId. |
| `data[].name` | string|null | Human-readable name for the resource or event. The exact meaning depends on the endpoint. |
| `data[].email` | string | Team member email. |
| `data[].image` | string|null | Profile image URL. |
| `data[].role` | string | `owner`, `member`, or `viewer`. |
| `data[].joinedAt` | string | Membership creation timestamp. |

### 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/websites/{websiteId}/team" \
  -H "Authorization: Bearer dft_xxx"
```

### Success response

```json
{
  "status": "success",
  "data": [{
    "userId": "665f0b3c4d2e1a0012345678",
    "name": "Jane Doe",
    "email": "jane@example.com",
    "image": "https://example.com/avatar.png",
    "role": "owner",
    "joinedAt": "2026-05-21T00:00:00.000Z"
  }]
}
```