> **This method is rolling out in `crm 26.2100.0`.** It is not available in every Bitrix24 account. If the method is not enabled yet, the API returns `422 METHOD_NOT_YET_AVAILABLE`.

## List end-to-end analytics channels

`GET /v1/crm-tracking/channels`

List end-to-end analytics channels used to configure how customer interactions are collected.

Requires the `crm` scope, the `crm-tracking-v3` flag, and the feature enabled in the Bitrix24 account. `READONLY` keys can read this resource.

## Parameters

| Parameter | Type | Default | Description |
|---|---|---|---|
| `limit` (query) | number | `50` | Page size, an integer from 1 to 500. |
| `offset` (query) | number | `0` | Number of records to skip, a non-negative integer. |

Pagination: each request returns one page. Increase `offset` by `limit` to request the next page. Sorting and additional filters are not supported.

## Examples

### curl — personal key

```bash
curl "https://vibecode.bitrix24.com/v1/crm-tracking/channels?limit=50&offset=0" \
  -H "X-Api-Key: YOUR_API_KEY"
```

### curl — OAuth application

```bash
curl "https://vibecode.bitrix24.com/v1/crm-tracking/channels?limit=50&offset=0" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN"
```

### JavaScript — personal key

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/crm-tracking/channels?limit=50&offset=0', {
  headers: { 'X-Api-Key': 'YOUR_API_KEY' },
})
const result = await res.json()
console.log(result)
```

### JavaScript — OAuth application

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/crm-tracking/channels?limit=50&offset=0', {
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})
const result = await res.json()
console.log(result)
```

## Response fields

| Field | Type | Description |
|---|---|---|
| `success` | boolean | `true` |
| `data` | array | Channels. |
| `data[].code` | string | Channel code. |
| `data[].name` | string | Channel name in the account language. |
| `data[].isConfigurable` | boolean | Whether the channel can be configured. |
| `data[].isConfigured` | boolean | Whether the channel is configured. |
| `meta.limit` | number | Requested page size. |
| `meta.offset` | number | Number of records skipped. |

## Response example

Channel names below illustrate an English-language account.

```json
{
  "success": true,
  "data": [
    {
      "code": "site24",
      "name": "Bitrix24 website",
      "isConfigurable": false,
      "isConfigured": true
    },
    {
      "code": "shop24",
      "name": "Bitrix24 online store",
      "isConfigurable": false,
      "isConfigured": true
    }
  ],
  "meta": {
    "limit": 50,
    "offset": 0
  }
}
```

## Error response example

400 — unsupported query parameter:

```json
{
  "success": false,
  "error": {
    "code": "UNKNOWN_FILTER_FIELD",
    "message": "Unknown query parameter"
  }
}
```

## Errors

| HTTP | Code | Description |
|---|---|---|
| 400 | `INVALID_PARAMS` | Invalid pagination. |
| 400 | `UNKNOWN_FILTER_FIELD` | An unsupported query parameter, filter, or sort was supplied. |
| 403 | `SCOPE_DENIED` | The key lacks the `crm` scope. |
| 401 | `TOKEN_MISSING` | The key has no configured tokens. |
| 422 | `METHOD_NOT_YET_AVAILABLE` | The flag is off or the method is not enabled in the account. `error.release` is `crm 26.2100.0`. |
| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 returned an invalid response. |

Other Bitrix24 refusal codes, HTTP statuses, and messages are preserved. For common API errors, see [Errors](/docs/errors).

## See also

- [List analytics sources](/docs/entities/crm-tracking/sources-list)
- [Get an analytics source](/docs/entities/crm-tracking/sources-get)
- [Update an analytics source](/docs/entities/crm-tracking/sources-update)