[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-infra\u002Fservers\u002Fb24-catalog-hide":3,"docs-tabs-infra\u002Fservers\u002Fb24-catalog-hide":6},{"content":4,"lastmod":5},"## Remove the app from Bitrix24\n\n`POST \u002Fv1\u002Finfra\u002Fservers\u002F:id\u002Fb24-catalog\u002Fhide`\n\nHides the app from employees in the Bitrix24 catalog and deletes the app chat together with its history. Access to the app and its links stay the same.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|:-----:|----------|\n| `id` (path) | string (UUID) | yes | Server ID from the [server list](.\u002Flist.md). The server must be managed by the API key used for the request |\n\nThe request body may be empty or `{}`. Unknown fields are ignored.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X POST -H \"X-Api-Key: YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" -d '{}' \\\n  https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Finfra\u002Fservers\u002FSERVER_ID\u002Fb24-catalog\u002Fhide\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X POST -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" -d '{}' \\\n  https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Finfra\u002Fservers\u002FSERVER_ID\u002Fb24-catalog\u002Fhide\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch(\n  `https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Finfra\u002Fservers\u002F${serverId}\u002Fb24-catalog\u002Fhide`,\n  {\n    method: 'POST',\n    headers: { 'X-Api-Key': 'YOUR_API_KEY', 'Content-Type': 'application\u002Fjson' },\n    body: '{}',\n  }\n)\nconst body = await res.json()\nif (!body.success) throw new Error(body.error.code)\nconsole.log(body.data.showInBitrix24, body.data.queued)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch(\n  `https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Finfra\u002Fservers\u002F${serverId}\u002Fb24-catalog\u002Fhide`,\n  {\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: '{}',\n  }\n)\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` when the choice is saved |\n| `data.queued` | boolean | `true` if the card exists and its deletion has been queued. `false` if there is no card |\n| `data.showInBitrix24` | string | The saved choice. Always `NO` |\n\n## Response example\n\nCard deletion has been queued:\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"queued\": true,\n    \"showInBitrix24\": \"NO\"\n  }\n}\n```\n\n## Error response example\n\n404 — the server was not found or is managed by another API key:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"NOT_FOUND\",\n    \"message\": \"Server not found\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 404 | `NOT_FOUND` | The server does not exist, has been deleted, or is managed by another API key |\n| 404 | `NOT_FOUND` | The server was deleted before the choice was saved |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header is missing |\n| 401 | `INVALID_API_KEY` | The key is not recognized |\n| 403 | `INFRA_FORBIDDEN_FOR_COWORK_KEY` | A Cowork key cannot perform write operations. Use a [project key for deploy](\u002Fdocs\u002Fcowork\u002Fdeploy-key) |\n| 429 | `RATE_LIMITED` | Request limit exceeded. Retry after the pause specified in the `Retry-After` header |\n\nFor the full list of shared API errors, see [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n- **The card is deleted in the background.** Check the [server state](.\u002Fget.md) for completion: `b24CatalogSync.itemId` becomes `null` and `pendingOp` is no longer `DELETE`.\n- **You can hide the app before its card is created.** The pending publication is canceled and the choice becomes `NO`. Subsequent deployments keep this choice and do not create a card.\n- **Publishing again creates a new chat.** After deletion, [show the app again](.\u002Fb24-catalog-publish.md) if employees need it. The new chat will be empty; the previous history is not restored. While deletion is pending, publishing returns `409 CATALOG_DELETE_PENDING` and the choice stays `NO`.\n- **Repeating the call keeps the choice.** If the card no longer exists, the method returns `queued: false` and `showInBitrix24: \"NO\"`.\n\n## See also\n\n- [Publish the app to the Bitrix24 catalog](.\u002Fb24-catalog-publish.md)\n- [Get a server](.\u002Fget.md)\n- [Deploy an app](\u002Fdocs\u002Finfra\u002Fdeploy\u002Fdeploy)\n","2026-11-17",{},1795000544856]