[{"data":1,"prerenderedAt":11},["ShallowReactive",2],{"docs-openlines\u002Fquick-replies":3,"docs-tabs-openlines\u002Fquick-replies":6},{"content":4,"lastmod":5},"# Open Channel quick replies\n\nReply templates that an Open Channel operator inserts into a conversation with a client. This subsection reads a channel's replies and sections, and creates, edits and deletes replies.\n\nBitrix24 API: `imopenlines.v2.QuickReply.*`\nScope: `imopenlines`\n\n## Operations\n\n- [List quick replies](.\u002Fquick-replies\u002Flist.md) — `GET \u002Fv1\u002Fopenline-configs\u002F:lineId\u002Fquick-replies`\n- [Create a quick reply](.\u002Fquick-replies\u002Fcreate.md) — `POST \u002Fv1\u002Fopenline-configs\u002F:lineId\u002Fquick-replies`\n- [Update a quick reply](.\u002Fquick-replies\u002Fupdate.md) — `PATCH \u002Fv1\u002Fopenline-configs\u002F:lineId\u002Fquick-replies\u002F:id`\n- [Delete a quick reply](.\u002Fquick-replies\u002Fdelete.md) — `DELETE \u002Fv1\u002Fopenline-configs\u002F:lineId\u002Fquick-replies\u002F:id`\n\n## Typical scenario\n\n1. Get the channel ID: [`GET \u002Fv1\u002Fopenline-configs`](\u002Fdocs\u002Fopenlines\u002Fconfig\u002Flist).\n2. Read the channel's replies and sections: [`GET \u002Fv1\u002Fopenline-configs\u002F:lineId\u002Fquick-replies`](.\u002Fquick-replies\u002Flist.md).\n3. Create, edit or delete a reply in this channel: [`POST`](.\u002Fquick-replies\u002Fcreate.md), [`PATCH`](.\u002Fquick-replies\u002Fupdate.md), [`DELETE`](.\u002Fquick-replies\u002Fdelete.md).\n\n## See also\n\n- [Open Channel configurations](\u002Fdocs\u002Fopenlines\u002Fconfig)\n- [Open Channels](\u002Fdocs\u002Fopenlines)\n","2026-10-19",{"quick-replies\u002Flist.md":7,"quick-replies\u002Fcreate.md":8,"quick-replies\u002Fupdate.md":9,"quick-replies\u002Fdelete.md":10},"## List quick replies\n\n`GET \u002Fv1\u002Fopenline-configs\u002F:lineId\u002Fquick-replies`\n\nReturns an Open Channel's quick replies together with its sections and the key user's permissions to view and create replies. Use the method to find a reply by text, get a reply ID to edit it, or get a section ID to create a reply.\n\nThe generic `filter` parameter is not applied by this endpoint. By default, the API preserves the previous HTTP 200 response and data, adds `Warning: 299 - \"filter is not supported on this endpoint and was ignored\"`, and records unsupported-filter use in the server log.\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|----------|-----|:-----:|-----------|----------|\n| `lineId` (path) | integer | yes | — | Open Channel ID. List: [`GET \u002Fv1\u002Fopenline-configs`](\u002Fdocs\u002Fopenlines\u002Fconfig\u002Flist) |\n| `search` (query) | string | no | — | Search string matched against the reply name and text |\n| `sectionId` (query) | integer | no | — | ID of a section of this channel from `data.sections`. Returns only the replies in this section |\n| `offset` (query) | integer | no | `0` | How many records to skip from the start of the result set |\n| `limit` (query) | integer | no | `50` | How many records to return, from `0` to `50`. A value above `50` is reduced to `50`. With `0` the `replies` array is empty, while `totalCount`, `sections` and `permissions` are returned |\n\n**Pagination.** One call returns at most 50 replies. To read all of them, increase `offset` by the number of records received until `offset` plus the length of `replies` reaches `totalCount`.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fopenline-configs\u002F3\u002Fquick-replies?limit=20\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fopenline-configs\u002F3\u002Fquick-replies?limit=20\" \\\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(\n  'https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fopenline-configs\u002F3\u002Fquick-replies?limit=20',\n  { headers: { 'X-Api-Key': 'YOUR_API_KEY' } }\n)\nconst { data } = await res.json()\nconsole.log(`Replies: ${data.totalCount}`, data.replies)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch(\n  'https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fopenline-configs\u002F3\u002Fquick-replies?limit=20',\n  {\n    headers: {\n      'X-Api-Key': 'YOUR_APP_KEY',\n      'Authorization': 'Bearer USER_SESSION_TOKEN',\n    },\n  }\n)\nconst { data } = await res.json()\nconsole.log(`Replies: ${data.totalCount}`, data.replies)\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` on success |\n| `data.replies` | array | Quick replies on the current page of the result set |\n| `data.replies[].id` | integer | Quick reply ID |\n| `data.replies[].name` | string | Reply name |\n| `data.replies[].text` | string | Reply text |\n| `data.replies[].sectionId` | integer | Section ID. `0` means the reply has no section |\n| `data.replies[].canEdit` | boolean | Whether the key user can edit the reply |\n| `data.replies[].rating` | number \\| string | Reply rating |\n| `data.sections` | array | All quick reply sections of this channel |\n| `data.sections[].id` | integer | Section ID. Passed in `sectionId` |\n| `data.sections[].name` | string | Section name |\n| `data.sections[].code` | string | Section symbolic code |\n| `data.totalCount` | integer | How many replies match `search` and `sectionId`, regardless of `offset` and `limit` |\n| `data.permissions.canView` | boolean | Whether the key user can view the channel's quick replies. With `false`, an empty `replies` array does not mean the channel has no replies |\n| `data.permissions.canCreate` | boolean | Whether the key user can create quick replies in the channel |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"replies\": [\n      {\n        \"id\": 7277,\n        \"name\": \"Hello, an operator will reply within a minute\",\n        \"text\": \"Hello, an operator will reply within a minute\",\n        \"sectionId\": 123,\n        \"canEdit\": true,\n        \"rating\": 1\n      },\n      {\n        \"id\": 7279,\n        \"name\": \"Delivery within the city takes one to two business days\",\n        \"text\": \"Delivery within the city takes one to two business days\",\n        \"sectionId\": 0,\n        \"canEdit\": true,\n        \"rating\": 1\n      }\n    ],\n    \"sections\": [\n      { \"id\": 123, \"name\": \"Greeting\", \"code\": \"GREETING\" },\n      { \"id\": 125, \"name\": \"Payment\", \"code\": \"PAYMENT\" },\n      { \"id\": 127, \"name\": \"Delivery\", \"code\": \"DELIVERY\" },\n      { \"id\": 129, \"name\": \"General\", \"code\": \"COMMON\" }\n    ],\n    \"totalCount\": 2,\n    \"permissions\": {\n      \"canView\": true,\n      \"canCreate\": true\n    }\n  }\n}\n```\n\n## Error response example\n\n404 — there is no Open Channel with this `lineId`:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"ENTITY_NOT_FOUND\",\n    \"message\": \"Record not found\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 200 | `Warning: 299` | The filter is ignored by default; previous data is preserved and the warning is sent in the `Warning` header. |\n| 400 (strict mode only) | `UNSUPPORTED_FILTER` | The server mode is disabled by default; until it is enabled, the endpoint preserves HTTP 200 and the previous data. |\n| 400 | `INVALID_PARAMS` | `lineId` is not a positive integer |\n| 400 | `INVALID_PARAMS` | `offset` or `limit` is negative or not an integer, or `search` is not a string |\n| 400 | `INVALID_PARAMS` | `sectionId` is not a non-negative integer |\n| 400 | `INVALID_PARAMS` | A query string parameter is passed twice or in object form, for example `search=a&search=b` or `search[x]=a` |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was not passed |\n| 401 | `TOKEN_MISSING` | The key has no valid authorization in Bitrix24 |\n| 403 | `SCOPE_DENIED` | The key lacks the `imopenlines` scope |\n| 403 | `BITRIX_ACCESS_DENIED` | Bitrix24 denied access to the key user |\n| 404 | `ENTITY_NOT_FOUND` | There is no Open Channel with this `lineId` |\n| 422 | `BITRIX_ERROR` | Bitrix24 returned an error. The text is in `message` |\n| 429 | `RATE_LIMITED` | The method's own limit was exceeded. The overall platform ceiling is 120 requests per minute per portal and is split across platform replicas, so the code may arrive before the 120th request. The effective value is in the `x-ratelimit-limit` header |\n| 502 | `OPENLINE_OPERATOR_FAILED` | Bitrix24 returned a response of an unexpected shape |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable |\n| 503 | `BITRIX_TIMEOUT` | Bitrix24 did not respond in time. A read is safe to retry |\n\nFull list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n**Each channel has its own sections and replies.** `data.sections` lists only the sections of the channel from the path, and passing another channel's section ID in `sectionId` returns no replies here. Filtering by a non-existent section returns an empty `replies` array with `totalCount: 0`, not an error.\n\n## See also\n\n- [Create a quick reply](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Fcreate)\n- [Update a quick reply](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Fupdate)\n- [Delete a quick reply](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Fdelete)\n- [Open Channel quick replies](\u002Fdocs\u002Fopenlines\u002Fquick-replies)\n- [List Open Channel configurations](\u002Fdocs\u002Fopenlines\u002Fconfig\u002Flist)\n","## Create a quick reply\n\n`POST \u002Fv1\u002Fopenline-configs\u002F:lineId\u002Fquick-replies`\n\nAdds a quick reply to an Open Channel — a prepared text that the operator inserts into a conversation with a client.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|:-----:|----------|\n| `lineId` (path) | integer | yes | Open Channel ID. List: [`GET \u002Fv1\u002Fopenline-configs`](\u002Fdocs\u002Fopenlines\u002Fconfig\u002Flist) |\n\n## Request fields (body)\n\nThe body is passed flat, without a `fields` wrapper.\n\n| Field | Type | Required | Description |\n|------|-----|:-----:|----------|\n| `text` | string | yes | Reply text. A string of whitespace only is not accepted |\n| `sectionId` | integer | no | ID of a section of the same channel from `data.sections` in the [`GET \u002Fv1\u002Fopenline-configs\u002F:lineId\u002Fquick-replies`](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Flist) response. Without the field the reply is created without a section, and `sectionId` in the response is `0` |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fopenline-configs\u002F3\u002Fquick-replies\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"text\": \"Delivery within the city takes one to two business days\",\n    \"sectionId\": 127\n  }'\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fopenline-configs\u002F3\u002Fquick-replies\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"text\": \"Delivery within the city takes one to two business days\",\n    \"sectionId\": 127\n  }'\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fopenline-configs\u002F3\u002Fquick-replies', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({\n    text: 'Delivery within the city takes one to two business days',\n    sectionId: 127,\n  }),\n})\nconst { data } = await res.json()\nconsole.log('Reply ID:', data.id)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fopenline-configs\u002F3\u002Fquick-replies', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({\n    text: 'Delivery within the city takes one to two business days',\n    sectionId: 127,\n  }),\n})\nconst { data } = await res.json()\nconsole.log('Reply ID:', data.id)\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` on success |\n| `data` | object | The created quick reply. Same fields as a `data.replies[]` record in the [quick reply list](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Flist) |\n| `data.id` | integer | ID of the created reply. Needed to [update](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Fupdate) and [delete](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Fdelete) it |\n| `data.name` | string | Reply name — the first 100 characters of `text` |\n| `data.text` | string | Reply text |\n| `data.sectionId` | integer | Section ID. `0` means the reply has no section |\n| `data.canEdit` | boolean | Whether the key's user can edit the reply |\n| `data.rating` | number \\| string | Reply rating. A new reply has `1` |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": 7279,\n    \"name\": \"Delivery within the city takes one to two business days\",\n    \"text\": \"Delivery within the city takes one to two business days\",\n    \"sectionId\": 127,\n    \"canEdit\": true,\n    \"rating\": 1\n  }\n}\n```\n\n## Error response example\n\n400 — `text` was not passed or contains only whitespace:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"MISSING_REQUIRED_FIELDS\",\n    \"message\": \"text must be a non-empty string\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `MISSING_REQUIRED_FIELDS` | `text` was not passed, is empty, or consists of whitespace |\n| 400 | `INVALID_PARAMS` | `lineId` is not a positive integer |\n| 400 | `INVALID_PARAMS` | `sectionId` is not a non-negative integer |\n| 400 | `INVALID_PARAMS` | `sectionId` is not `0` and is not among `data.sections` of this channel. The reply is not created |\n| 400 | `INVALID_PARAMS` | The request body is not a JSON object |\n| 400 | `INVALID_JSON_BODY` | The request body cannot be parsed as JSON |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was not passed |\n| 401 | `TOKEN_MISSING` | The key has no valid authorization in Bitrix24 |\n| 403 | `SCOPE_DENIED` | The key lacks the `imopenlines` scope |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is in read-only mode |\n| 403 | `BITRIX_ACCESS_DENIED` | `sectionId` is passed, but the channel's quick replies are unavailable to the key user: no permission to view them, or the plan does not include them |\n| 403 | `BITRIX_ACCESS_DENIED` | Bitrix24 denied access to the key's user |\n| 404 | `ENTITY_NOT_FOUND` | There is no Open Channel with this `lineId` |\n| 422 | `BITRIX_ERROR` | Bitrix24 returned an error. The text is in `message` |\n| 429 | `RATE_LIMITED` | The method's own limit was exceeded. The overall platform ceiling is 120 requests per minute per portal and is split across platform replicas, so the code may arrive before the 120th request. The effective value is in the `x-ratelimit-limit` header |\n| 502 | `OPENLINE_OPERATOR_FAILED` | Bitrix24 returned a response of an unexpected shape |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable |\n| 503 | `BITRIX_TIMEOUT` | Bitrix24 did not respond in time. The reply may have been created: check the [list of replies](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Flist) before retrying |\n\nFull list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n**The name comes from the text only.** The `name` field in the request body is ignored, and the reply name is built from `text`.\n\n## See also\n\n- [List quick replies](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Flist)\n- [Update a quick reply](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Fupdate)\n- [Delete a quick reply](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Fdelete)\n- [Open Channel quick replies](\u002Fdocs\u002Fopenlines\u002Fquick-replies)\n- [List Open Channel configurations](\u002Fdocs\u002Fopenlines\u002Fconfig\u002Flist)\n","## Update a quick reply\n\n`PATCH \u002Fv1\u002Fopenline-configs\u002F:lineId\u002Fquick-replies\u002F:id`\n\nReplaces the text of an Open Channel quick reply and, if needed, moves it to another section or removes it from its section.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|:-----:|----------|\n| `lineId` (path) | integer | yes | Open Channel ID. List: [`GET \u002Fv1\u002Fopenline-configs`](\u002Fdocs\u002Fopenlines\u002Fconfig\u002Flist) |\n| `id` (path) | integer | yes | ID of a quick reply in this channel. List: `data.replies[].id` in the [`GET \u002Fv1\u002Fopenline-configs\u002F:lineId\u002Fquick-replies`](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Flist) response |\n\n## Request fields (body)\n\nThe body is passed flat, without a `fields` wrapper.\n\n| Field | Type | Required | Description |\n|------|-----|:-----:|----------|\n| `text` | string | yes | The full new reply text. A string of whitespace only is not accepted |\n| `sectionId` | integer | no | ID of a section in the same channel from `data.sections` in the [`GET \u002Fv1\u002Fopenline-configs\u002F:lineId\u002Fquick-replies`](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Flist) response. Without the field the reply's section does not change; `0` removes the reply from its section |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X PATCH \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fopenline-configs\u002F3\u002Fquick-replies\u002F7277\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"text\": \"Hello, an operator will reply within a minute\",\n    \"sectionId\": 123\n  }'\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X PATCH \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fopenline-configs\u002F3\u002Fquick-replies\u002F7277\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"text\": \"Hello, an operator will reply within a minute\",\n    \"sectionId\": 123\n  }'\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fopenline-configs\u002F3\u002Fquick-replies\u002F7277', {\n  method: 'PATCH',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({\n    text: 'Hello, an operator will reply within a minute',\n    sectionId: 123,\n  }),\n})\nconst { data } = await res.json()\nconsole.log(data.name, data.sectionId)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fopenline-configs\u002F3\u002Fquick-replies\u002F7277', {\n  method: 'PATCH',\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({\n    text: 'Hello, an operator will reply within a minute',\n    sectionId: 123,\n  }),\n})\nconst { data } = await res.json()\nconsole.log(data.name, data.sectionId)\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` on success |\n| `data` | object | The quick reply after the edit. Same fields as a `data.replies[]` record in the [quick reply list](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Flist) |\n| `data.id` | integer | Reply ID, matches `id` from the path |\n| `data.name` | string | Reply name — the first 100 characters of the new `text` |\n| `data.text` | string | Reply text after the update |\n| `data.sectionId` | integer | Section ID after the update. `0` means the reply has no section |\n| `data.canEdit` | boolean | Whether the key user can edit the reply |\n| `data.rating` | number \\| string | Reply rating |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": 7277,\n    \"name\": \"Hello, an operator will reply within a minute\",\n    \"text\": \"Hello, an operator will reply within a minute\",\n    \"sectionId\": 123,\n    \"canEdit\": true,\n    \"rating\": 1\n  }\n}\n```\n\n## Error response example\n\n404 — the channel from the path has no reply with this `id`:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"ENTITY_NOT_FOUND\",\n    \"message\": \"Quick reply not found in this line\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `MISSING_REQUIRED_FIELDS` | `text` was not passed, is empty, or consists of whitespace |\n| 400 | `INVALID_PARAMS` | `lineId` or `id` is not a positive integer |\n| 400 | `INVALID_PARAMS` | `sectionId` is not a non-negative integer |\n| 400 | `INVALID_PARAMS` | `sectionId` is not `0`, differs from the reply's current section and is not among `data.sections` of this channel. The reply is not changed |\n| 400 | `INVALID_PARAMS` | The request body is not a JSON object |\n| 400 | `INVALID_JSON_BODY` | The request body cannot be parsed as JSON |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was not passed |\n| 401 | `TOKEN_MISSING` | The key has no valid authorization in Bitrix24 |\n| 403 | `SCOPE_DENIED` | The key lacks the `imopenlines` scope |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is in read-only mode |\n| 403 | `BITRIX_ACCESS_DENIED` | The key user has no permission to view the channel's quick replies |\n| 403 | `BITRIX_ACCESS_DENIED` | Bitrix24 denied access to the key user when saving |\n| 404 | `ENTITY_NOT_FOUND` | Message `Quick reply not found in this line`: the channel from the path has no reply with this `id`, including when the reply belongs to another channel |\n| 404 | `ENTITY_NOT_FOUND` | Message `Record not found`: there is no Open Channel with this `lineId` |\n| 422 | `BITRIX_ERROR` | Bitrix24 returned an error. The text is in `message` |\n| 429 | `RATE_LIMITED` | The method's own limit was exceeded. The overall platform ceiling is 120 requests per minute per portal and is split across platform replicas, so the code may arrive before the 120th request. The effective value is in the `x-ratelimit-limit` header |\n| 502 | `OPENLINE_OPERATOR_FAILED` | Bitrix24 returned a response of an unexpected shape |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable |\n| 503 | `BITRIX_TIMEOUT` | Bitrix24 did not respond in time. The update may have been saved: check the [list of replies](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Flist) before retrying |\n\nFull list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## See also\n\n- [List quick replies](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Flist)\n- [Create a quick reply](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Fcreate)\n- [Delete a quick reply](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Fdelete)\n- [Open Channel quick replies](\u002Fdocs\u002Fopenlines\u002Fquick-replies)\n- [List Open Channel configurations](\u002Fdocs\u002Fopenlines\u002Fconfig\u002Flist)\n","## Delete a quick reply\n\n`DELETE \u002Fv1\u002Fopenline-configs\u002F:lineId\u002Fquick-replies\u002F:id`\n\nDeletes an Open Channel quick reply by its ID, provided the reply belongs to the channel specified in the request path. A deleted reply cannot be restored through the API — create a new one if needed.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|:-----:|----------|\n| `lineId` (path) | integer | yes | Open Channel ID. List: [`GET \u002Fv1\u002Fopenline-configs`](\u002Fdocs\u002Fopenlines\u002Fconfig\u002Flist) |\n| `id` (path) | integer | yes | ID of a quick reply in this channel. List: [`GET \u002Fv1\u002Fopenline-configs\u002F:lineId\u002Fquick-replies`](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Flist), field `data.replies[].id` |\n\nThe request has no body.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X DELETE \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fopenline-configs\u002F1\u002Fquick-replies\u002F7275\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X DELETE \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fopenline-configs\u002F1\u002Fquick-replies\u002F7275\" \\\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(\n  'https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fopenline-configs\u002F1\u002Fquick-replies\u002F7275',\n  { method: 'DELETE', headers: { 'X-Api-Key': 'YOUR_API_KEY' } }\n)\nconst { success, data } = await res.json()\nconsole.log(data.deleted)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch(\n  'https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fopenline-configs\u002F1\u002Fquick-replies\u002F7275',\n  {\n    method: 'DELETE',\n    headers: {\n      'X-Api-Key': 'YOUR_APP_KEY',\n      'Authorization': 'Bearer USER_SESSION_TOKEN',\n    },\n  }\n)\nconst { success, data } = await res.json()\nconsole.log(data.deleted)\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` on successful deletion |\n| `data.id` | integer | ID of the deleted quick reply |\n| `data.deleted` | boolean | Always `true` |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": 7275,\n    \"deleted\": true\n  }\n}\n```\n\n## Error response example\n\n404 — the `lineId` channel has no quick reply with this `id`:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"ENTITY_NOT_FOUND\",\n    \"message\": \"Quick reply not found in this line\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `INVALID_PARAMS` | `lineId` or `id` is not a positive integer |\n| 400 | `INVALID_PARAMS` | The request body is not a JSON object |\n| 400 | `INVALID_JSON_BODY` | The request body cannot be parsed as JSON |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was not passed |\n| 401 | `TOKEN_MISSING` | The key has no authorization on the Bitrix24 portal. For an application key, `Authorization: Bearer` was not passed |\n| 403 | `SCOPE_DENIED` | The key lacks the `imopenlines` scope |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is in read-only mode |\n| 403 | `BITRIX_ACCESS_DENIED` | The employee the call runs as cannot view this channel's quick replies |\n| 403 | `BITRIX_ACCESS_DENIED` | Bitrix24 denied the employee permission to delete the reply |\n| 404 | `ENTITY_NOT_FOUND` | Message `Quick reply not found in this line`: the channel has no reply with this `id`. The same response is returned for the `id` of another channel's reply and for a repeated deletion |\n| 404 | `ENTITY_NOT_FOUND` | Message `Record not found`: there is no Open Channel with this `lineId` |\n| 422 | `BITRIX_ERROR` | Bitrix24 returned an error. The text is in `message` |\n| 429 | `RATE_LIMITED` | The method's own limit was exceeded. The overall platform ceiling is 120 requests per minute per portal and is split across platform replicas, so the code may arrive before the 120th request. The effective value is in the `x-ratelimit-limit` header |\n| 502 | `OPENLINE_OPERATOR_FAILED` | Bitrix24 did not confirm the deletion or returned the channel's reply list in an unexpected shape. Check the [list of quick replies](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Flist) before retrying |\n| 502 | `BITRIX_UNAVAILABLE` | The Bitrix24 portal is unavailable |\n| 503 | `BITRIX_TIMEOUT` | Bitrix24 did not respond in time, and the outcome is unknown. Check the [list of quick replies](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Flist) before retrying |\n\nFull list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## See also\n\n- [List quick replies](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Flist)\n- [Create a quick reply](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Fcreate)\n- [Update a quick reply](\u002Fdocs\u002Fopenlines\u002Fquick-replies\u002Fupdate)\n- [Open Channel quick replies](\u002Fdocs\u002Fopenlines\u002Fquick-replies)\n- [List Open Channel configurations](\u002Fdocs\u002Fopenlines\u002Fconfig\u002Flist)\n",1795000565716]