For AI agents: markdown of this page — /docs-content-en/entities/crm-tracking/channels-list.md documentation index — /llms.txt

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
Parameterlimit (query) Typenumber Default50 DescriptionPage size, an integer from 1 to 500.
Parameteroffset (query) Typenumber Default0 DescriptionNumber 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

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

curl — OAuth application

Terminal 
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
Fieldsuccess Typeboolean Descriptiontrue
Fielddata Typearray DescriptionChannels.
Fielddata[].code Typestring DescriptionChannel code.
Fielddata[].name Typestring DescriptionChannel name in the account language.
Fielddata[].isConfigurable Typeboolean DescriptionWhether the channel can be configured.
Fielddata[].isConfigured Typeboolean DescriptionWhether the channel is configured.
Fieldmeta.limit Typenumber DescriptionRequested page size.
Fieldmeta.offset Typenumber DescriptionNumber 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
HTTP400 CodeINVALID_PARAMS DescriptionInvalid pagination.
HTTP400 CodeUNKNOWN_FILTER_FIELD DescriptionAn unsupported query parameter, filter, or sort was supplied.
HTTP403 CodeSCOPE_DENIED DescriptionThe key lacks the crm scope.
HTTP401 CodeTOKEN_MISSING DescriptionThe key has no configured tokens.
HTTP422 CodeMETHOD_NOT_YET_AVAILABLE DescriptionThe flag is off or the method is not enabled in the account. error.release is crm 26.2100.0.
HTTP502 CodeBITRIX_UNAVAILABLE DescriptionBitrix24 returned an invalid response.

Other Bitrix24 refusal codes, HTTP statuses, and messages are preserved. For common API errors, see Errors.

See also