[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-entities\u002Fcrm-emails\u002Fget":3,"docs-tabs-entities\u002Fcrm-emails\u002Fget":6},{"content":4,"lastmod":5},"## Get CRM e-mail content\n\n`GET \u002Fv1\u002Fcrm-emails\u002F:activityId`\n\nRead the text of a CRM e-mail and its record bindings. Use the e-mail activity identifier from the e-mail list.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|---|---|---|---|\n| `activityId` (path) | integer | yes | Activity identifier from the [e-mail list](.\u002Flist.md), not a Mail module message identifier. |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X GET \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fcrm-emails\u002F1203\" \\\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-emails\u002F1203\" \\\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 response = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fcrm-emails\u002F1203', {\n  method: 'GET',\n  headers: {\"X-Api-Key\": \"YOUR_API_KEY\"},\n})\nconst result = await response.json()\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst response = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fcrm-emails\u002F1203', {\n  method: 'GET',\n  headers: {\"X-Api-Key\": \"YOUR_APP_KEY\", \"Authorization\": \"Bearer USER_SESSION_TOKEN\"},\n})\nconst result = await response.json()\n```\n\n## Response fields\n\n| Field | Description |\n|---|---|\n| `data.id` | Identifier. |\n| `data.subject` | E-mail subject. |\n| `data.dateTime` | Date and time, or `null`. |\n| `data.isIncoming` | Whether the e-mail is incoming. |\n| `data.from` | Sender. |\n| `data.to` | Primary recipients. |\n| `data.cc` | CC recipients. |\n| `data.bcc` | BCC recipients. |\n| `data.body` | Plain text e-mail body. |\n| `data.isBodyTruncated` | Whether Bitrix24 truncated the body. |\n| `data.bindings[].entityTypeId` | Linked CRM record type. |\n| `data.bindings[].entityId` | Linked CRM record identifier. |\n\n## Response example\n\nResponse structure with neutral sample data.\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": 1203,\n    \"subject\": \"Integration request\",\n    \"dateTime\": \"2026-10-30T10:00:00+00:00\",\n    \"isIncoming\": true,\n    \"from\": \"sender@example.com\",\n    \"to\": [\n      \"reader@example.com\"\n    ],\n    \"cc\": [],\n    \"bcc\": [],\n    \"body\": \"Hello\",\n    \"isBodyTruncated\": false,\n    \"bindings\": [\n      {\n        \"entityTypeId\": 2,\n        \"entityId\": 741\n      }\n    ]\n  }\n}\n```\n\n## Error response example\n\n400 — unknown query parameter:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"UNKNOWN_FILTER_FIELD\",\n    \"message\": \"Unknown query parameter\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|---|---|---|\n| 400 | `INVALID_PARAMS` | Invalid type or identifier. |\n| 400 | `UNKNOWN_FILTER_FIELD` | Unknown query parameter. |\n| 401 | `TOKEN_MISSING` | The key has no Bitrix24 credentials. |\n| 403 | `SCOPE_DENIED` | The `crm` scope is required. |\n| 404 | `ENTITY_NOT_FOUND` | The record is absent or inaccessible. |\n| 404 | `CRM_EMAIL_ACTIVITY_NOT_FOUND` | The e-mail activity was not found. |\n| 422 | `METHOD_NOT_YET_AVAILABLE` | The method is absent on the account. `error.release` names the required release. |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable or returned an invalid response shape. |\n\nOther Bitrix24 refusals retain their original code and message. Common [API errors](\u002Fdocs\u002Ferrors).\n\n## Known behavior\n\nThese are CRM activity e-mails. The [Mail module](\u002Fdocs\u002Fmail) uses different message identifiers.\n\n## See also\n\n- [CRM settings](\u002Fdocs\u002Fentities\u002Fcrm-settings)\n- [CRM e-mails](\u002Fdocs\u002Fentities\u002Fcrm-emails)\n","2026-11-03",{},1794739350883]