[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-entities\u002Fcrm-enums\u002Fowner-types":3,"docs-tabs-entities\u002Fcrm-enums\u002Fowner-types":6},{"content":4,"lastmod":5},"## CRM entity types\n\n`GET \u002Fv1\u002Fcrm-enums\u002Fowner-types`\n\nReference list of the CRM entity types on the Bitrix24 account, smart processes included. Use it to map a numeric entity type to its letter code and back.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fcrm-enums\u002Fowner-types\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fcrm-enums\u002Fowner-types\" \\\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-enums\u002Fowner-types', {\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n  },\n})\n\nconst { data } = await res.json()\nconst byShortCode = Object.fromEntries(data.map((type) => [type.symbolCodeShort, type.id]))\nconsole.log(byShortCode.D) \u002F\u002F 2\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fcrm-enums\u002Fowner-types', {\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\n\nconst { data } = await res.json()\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` on a successful request |\n| `data` | array | CRM entity types |\n| `data[].id` | number | Type ID. Matches `entityTypeId` in CRM routes, for example in [`\u002Fv1\u002Fitems\u002F:entityTypeId`](\u002Fdocs\u002Fentities\u002Fitems) |\n| `data[].name` | string | Type name in the Bitrix24 account language |\n| `data[].symbolCode` | string \\| null | Symbolic code, for example `DEAL`, `SMART_INVOICE`, `DYNAMIC_1038` |\n| `data[].symbolCodeShort` | string \\| null | Short code. Matches the `ownerType` of product rows, for example [`D` for a deal](\u002Fdocs\u002Fentities\u002Fdeals\u002Fproducts-get) |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": [\n    { \"id\": 1, \"name\": \"Lead\", \"symbolCode\": \"LEAD\", \"symbolCodeShort\": \"L\" },\n    { \"id\": 2, \"name\": \"Deal\", \"symbolCode\": \"DEAL\", \"symbolCodeShort\": \"D\" },\n    { \"id\": 31, \"name\": \"Invoice\", \"symbolCode\": \"SMART_INVOICE\", \"symbolCodeShort\": \"SI\" },\n    { \"id\": 1038, \"name\": \"No fields\", \"symbolCode\": \"DYNAMIC_1038\", \"symbolCodeShort\": \"T40e\" }\n  ]\n}\n```\n\nThe example shows 4 of the 17 types returned by the test Bitrix24 account.\n\n## Error response example\n\n401 — the `X-Api-Key` header is missing:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"MISSING_API_KEY\",\n    \"message\": \"API key required. Pass via X-Api-Key header.\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 403 | `BITRIX_ACCESS_DENIED` | The key's user has no permission to read the reference list in Bitrix24 |\n| 422 | `BITRIX_ERROR` | Bitrix24 rejected the request. The reason is in `message` |\n| 429 | `RATE_LIMITED` | Bitrix24 request rate exceeded, retry in 1-2 seconds |\n| 502 | `BITRIX_RESPONSE_INVALID` | Bitrix24 returned the reference list in an unexpected shape |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable: it returned a server error or the connection dropped |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header is missing |\n| 401 | `TOKEN_MISSING` | The API key has no Bitrix24 tokens configured |\n| 403 | `SCOPE_DENIED` | The API key lacks the `crm` scope |\n\nFull list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n- **Smart processes are included in the list.** Their `symbolCode` is `DYNAMIC_` plus `id`, and `symbolCodeShort` is the letter `T` plus `id` in hexadecimal: for type `1038` it is `T40e`. Each Bitrix24 account has its own set of smart processes.\n- **Query parameters are ignored.** The method takes no parameters, and any passed in the URL do not affect the response.\n\n## See also\n\n- [CRM address types](\u002Fdocs\u002Fentities\u002Fcrm-enums\u002Faddress-types)\n- [CRM enums](\u002Fdocs\u002Fentities\u002Fcrm-enums)\n- [Smart process items](\u002Fdocs\u002Fentities\u002Fitems)\n- [Deal product rows](\u002Fdocs\u002Fentities\u002Fdeals\u002Fproducts-get)\n","2026-10-15",{},1794739351751]