## Get CRM e-mail content

`GET /v1/crm-emails/:activityId`

Read the text of a CRM e-mail and its record bindings. Use the e-mail activity identifier from the e-mail list.

## Parameters

| Parameter | Type | Required | Description |
|---|---|---|---|
| `activityId` (path) | integer | yes | Activity identifier from the [e-mail list](./list.md), not a Mail module message identifier. |

## Examples

### curl — personal key

```bash
curl -X GET "https://vibecode.bitrix24.com/v1/crm-emails/1203" \
  -H "X-Api-Key: YOUR_API_KEY"
```

### curl — OAuth application

```bash
curl -X GET "https://vibecode.bitrix24.com/v1/crm-emails/1203" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN"
```

### JavaScript — personal key

```javascript
const response = await fetch('https://vibecode.bitrix24.com/v1/crm-emails/1203', {
  method: 'GET',
  headers: {"X-Api-Key": "YOUR_API_KEY"},
})
const result = await response.json()
```

### JavaScript — OAuth application

```javascript
const response = await fetch('https://vibecode.bitrix24.com/v1/crm-emails/1203', {
  method: 'GET',
  headers: {"X-Api-Key": "YOUR_APP_KEY", "Authorization": "Bearer USER_SESSION_TOKEN"},
})
const result = await response.json()
```

## Response fields

| Field | Description |
|---|---|
| `data.id` | Identifier. |
| `data.subject` | E-mail subject. |
| `data.dateTime` | Date and time, or `null`. |
| `data.isIncoming` | Whether the e-mail is incoming. |
| `data.from` | Sender. |
| `data.to` | Primary recipients. |
| `data.cc` | CC recipients. |
| `data.bcc` | BCC recipients. |
| `data.body` | Plain text e-mail body. |
| `data.isBodyTruncated` | Whether Bitrix24 truncated the body. |
| `data.bindings[].entityTypeId` | Linked CRM record type. |
| `data.bindings[].entityId` | Linked CRM record identifier. |

## Response example

Response structure with neutral sample data.

```json
{
  "success": true,
  "data": {
    "id": 1203,
    "subject": "Integration request",
    "dateTime": "2026-10-30T10:00:00+00:00",
    "isIncoming": true,
    "from": "sender@example.com",
    "to": [
      "reader@example.com"
    ],
    "cc": [],
    "bcc": [],
    "body": "Hello",
    "isBodyTruncated": false,
    "bindings": [
      {
        "entityTypeId": 2,
        "entityId": 741
      }
    ]
  }
}
```

## Error response example

400 — unknown query parameter:

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

## Errors

| HTTP | Code | Description |
|---|---|---|
| 400 | `INVALID_PARAMS` | Invalid type or identifier. |
| 400 | `UNKNOWN_FILTER_FIELD` | Unknown query parameter. |
| 401 | `TOKEN_MISSING` | The key has no Bitrix24 credentials. |
| 403 | `SCOPE_DENIED` | The `crm` scope is required. |
| 404 | `ENTITY_NOT_FOUND` | The record is absent or inaccessible. |
| 404 | `CRM_EMAIL_ACTIVITY_NOT_FOUND` | The e-mail activity was not found. |
| 422 | `METHOD_NOT_YET_AVAILABLE` | The method is absent on the account. `error.release` names the required release. |
| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable or returned an invalid response shape. |

Other Bitrix24 refusals retain their original code and message. Common [API errors](/docs/errors).

## Known behavior

These are CRM activity e-mails. The [Mail module](/docs/mail) uses different message identifiers.

## See also

- [CRM settings](/docs/entities/crm-settings)
- [CRM e-mails](/docs/entities/crm-emails)