[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-entities\u002Fcrm-emails\u002Flist":3,"docs-tabs-entities\u002Fcrm-emails\u002Flist":6},{"content":4,"lastmod":5},"## List CRM e-mails\n\n`GET \u002Fv1\u002Fdeals\u002F:id\u002Femails`\n\n`GET \u002Fv1\u002Fleads\u002F:id\u002Femails`\n\n`GET \u002Fv1\u002Fcontacts\u002F:id\u002Femails`\n\n`GET \u002Fv1\u002Fcompanies\u002F:id\u002Femails`\n\nRead one page of e-mails linked to a deal, lead, contact or company. Bitrix24 checks access to the record.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|---|---|---|---|\n| `id` (path) | integer | yes | Record identifier from [deals](\u002Fdocs\u002Fentities\u002Fdeals), [leads](\u002Fdocs\u002Fentities\u002Fleads), [contacts](\u002Fdocs\u002Fentities\u002Fcontacts) or [companies](\u002Fdocs\u002Fentities\u002Fcompanies). |\n| `limit` (query) | integer | no | Page size. The effective value is returned in `meta.limit`. |\n| `offset` (query) | integer | no | Offset from zero. Continue with `meta.nextOffset`. |\n| `isIncoming` (query) | boolean | no | `true` or `1` for incoming, `false` or `0` for outgoing. Omit for both. |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X GET \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fdeals\u002F741\u002Femails\" \\\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\u002Fdeals\u002F741\u002Femails\" \\\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\u002Fdeals\u002F741\u002Femails', {\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\u002Fdeals\u002F741\u002Femails', {\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 | Type | Description |\n|---|---|---|\n| `success` | boolean | `true` on success. |\n| `data` | array | E-mails on the page. |\n| `data[].id` | integer | Identifier. |\n| `data[].subject` | string | E-mail subject. |\n| `data[].dateTime` | string\u002Fnull | Date and time, or `null`. |\n| `data[].isIncoming` | boolean | Whether the e-mail is incoming. |\n| `data[].from` | string | Sender. |\n| `data[].to` | string[] | Primary recipients. |\n| `meta.returnedCount` | integer | Number of returned records. |\n| `meta.hasMore` | boolean | Whether another page is available. |\n| `meta.nextOffset` | integer\u002Fnull | Next page offset, or `null`. |\n| `meta.limit` | integer | Effective page size. |\n| `meta.offset` | integer | Effective offset. |\n\n## Response example\n\nResponse structure with neutral sample data.\n\n```json\n{\n  \"success\": true,\n  \"data\": [\n    {\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    }\n  ],\n  \"meta\": {\n    \"returnedCount\": 1,\n    \"hasMore\": false,\n    \"nextOffset\": null,\n    \"limit\": 50,\n    \"offset\": 0\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\nEach request reads one page. No collection total is supplied. Continue only by `meta.hasMore` and `meta.nextOffset`. Filtering, sorting and field selection are not supported.\n\n## See also\n\n- [CRM settings](\u002Fdocs\u002Fentities\u002Fcrm-settings)\n- [CRM e-mails](\u002Fdocs\u002Fentities\u002Fcrm-emails)\n","2026-11-05",{},1794739351023]