[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-entities\u002Fcrm-traces\u002Fv3-get":3,"docs-tabs-entities\u002Fcrm-traces\u002Fv3-get":6},{"content":4,"lastmod":5},"> **The method is rolling out in update `crm 26.2000.0`.** It is not available on every Bitrix24 account. If the method is not yet available on your account, the API returns `422 METHOD_NOT_YET_AVAILABLE` — this indicates that the update has not reached the account yet, rather than an integration error.\n\n## Get an analytics trace\n\n`GET \u002Fv1\u002Fcrm-traces\u002F:id`\n\nReads a visit, its source, channels and viewed pages by the trace identifier.\n\n> This operation requires the `crm-tracking-v3` flag and the REST v3 analytics capability enabled in the Bitrix24 account. The key needs the `crm` scope.\n\nA `READONLY` key can read this resource.\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|---|---|---|---|---|\n| `id` (path) | number | yes | — | Positive trace ID from the [list](\u002Fdocs\u002Fentities\u002Fcrm-traces\u002Fv3-list) or [create response](\u002Fdocs\u002Fentities\u002Fcrm-traces\u002Fv3-create). |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X GET \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fcrm-traces\u002F1\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X GET \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fcrm-traces\u002F1\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\"\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fcrm-traces\u002F1', {\n  \"method\": \"GET\",\n  \"headers\": {\n    \"X-Api-Key\": \"YOUR_API_KEY\"\n  }\n})\nconst result = await res.json()\nconsole.log(result)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fcrm-traces\u002F1', {\n  \"method\": \"GET\",\n  \"headers\": {\n    \"X-Api-Key\": \"YOUR_APP_KEY\",\n    \"Authorization\": \"Bearer USER_SESSION_TOKEN\"\n  }\n})\nconst result = await res.json()\nconsole.log(result)\n```\n\n## Response fields\n\n| Field | Type | Description |\n|---|---|---|\n| `success` | boolean | `true` |\n| `data` | object | One visit trace. |\n| `data.id` | number | Trace ID. |\n| `data.sourceId` | number or null | Analytics source ID. |\n| `data.createdTime` | string | Creation time, ISO 8601. |\n| `data.isMobile` | boolean | Whether the visit used a mobile device. |\n| `data.channels` | array | Channels with `code`, `value` fields. Text can be `null`. |\n| `data.pages` | array | Pages with `url`, `title`, `time` fields. Time is ISO 8601. Text can be `null`. |\n| `data.utm` | object or null | Tags `source`, `medium`, `campaign`, `content`, `term`, each a string or `null`. |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": 1,\n    \"sourceId\": 2,\n    \"createdTime\": \"2026-10-28T11:59:18+00:00\",\n    \"isMobile\": false,\n    \"channels\": [\n      {\n        \"code\": \"form\",\n        \"value\": \"5\"\n      }\n    ],\n    \"pages\": [\n      {\n        \"url\": \"https:\u002F\u002Fexample.com\u002Fp\",\n        \"title\": \"VIBE-PROBE page\",\n        \"time\": \"2026-10-28T10:00:00+00:00\"\n      }\n    ],\n    \"utm\": {\n      \"source\": \"vibeprobe\",\n      \"medium\": null,\n      \"campaign\": \"x\",\n      \"content\": null,\n      \"term\": null\n    }\n  }\n}\n```\n\n## Error response example\n\n404: trace not found. Error messages follow the Bitrix24 account language.\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"ENTITY_NOT_FOUND\",\n    \"message\": \"Entity with ID 1 was not found.\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|---|---|---|\n| 400 | `INVALID_PARAMS` | Invalid request type or shape, or an invalid ID. |\n| 403 | `SCOPE_DENIED` | Missing `crm` scope. |\n| 401 | `TOKEN_MISSING` | The key has no configured tokens. |\n| 422 | `METHOD_NOT_YET_AVAILABLE` | The platform flag is off or RestV3Tracking is not enabled on the Bitrix24 portal. `error.release` is `crm 26.2000.0`. |\n| 502 | `BITRIX_UNAVAILABLE` | Invalid Bitrix24 response. |\n| 400 | `UNKNOWN_FILTER_FIELD` | An unsupported query parameter was supplied. |\n| 404 | `ENTITY_NOT_FOUND` | The trace is absent or not readable. |\n| 403 | `BITRIX_REST_V3_EXCEPTION_ACCESSDENIEDEXCEPTION` | Insufficient permissions for linked CRM records. |\n\nOther Bitrix24 refusal codes, statuses and messages are preserved. See [Errors](\u002Fdocs\u002Ferrors) for common failures.\n\n## Known specifics\n\nCredential fragments in text fields are redacted. Page addresses without sensitive data are preserved unchanged.\n\n## See also\n\n- [List analytics traces](\u002Fdocs\u002Fentities\u002Fcrm-traces\u002Fv3-list)\n- [Create an analytics trace](\u002Fdocs\u002Fentities\u002Fcrm-traces\u002Fv3-create)\n- [Delete an analytics trace](\u002Fdocs\u002Fentities\u002Fcrm-traces\u002Fv3-delete)\n","2026-10-28",{},1794739360086]