[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-entities\u002Fcrm-settings\u002Flist":3,"docs-tabs-entities\u002Fcrm-settings\u002Flist":6},{"content":4,"lastmod":5},"## List CRM settings\n\n`GET \u002Fv1\u002Fcrm-settings`\n\nList the CRM settings readable by the key owner, with their current values and accepted value schemas.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X GET \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fcrm-settings\" \\\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-settings\" \\\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-settings', {\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-settings', {\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[]` | Array of readable settings. |\n| `data[].id` | Identifier. |\n| `data[].value` | JSON value with its original type. |\n| `data[].meta.title` | Setting title. |\n| `data[].meta.description` | Setting description. |\n| `data[].meta.schema` | Accepted value schema, validated by Bitrix24. |\n\n## Response example\n\nResponse structure with neutral sample data.\n\n```json\n{\n  \"success\": true,\n  \"data\": [\n    {\n      \"id\": \"crm.layout.file_previewer.enabled\",\n      \"value\": true,\n      \"meta\": {\n        \"title\": \"File preview\",\n        \"description\": \"Preview files\",\n        \"schema\": {\n          \"type\": \"boolean\"\n        }\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| 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\nAn object in `value` replaces the complete setting value. A successful write is not rolled back if its readback fails. Never blindly retry an ambiguous write failure: read the setting first.\n\n## See also\n\n- [CRM settings](\u002Fdocs\u002Fentities\u002Fcrm-settings)\n- [CRM e-mails](\u002Fdocs\u002Fentities\u002Fcrm-emails)\n","2026-11-03",{},1794739359079]